Jump to content

Chromebook ARC IP Addresses (100.115.x.x) Persisting After Disabling Android Apps


Recommended Posts

Posted (edited)

Hey everyone,

 

I'm encountering a persistent issue with my Chromebook and I'm hoping someone here might have some insight. I've noticed that my Chromebook is generating IP addresses in the 100.115.x.x range. After some research, I've determined that these IPs are associated with ARC (Android Runtime for Chrome), which handles Android app compatibility.

 

I've disabled Android apps and the Google Play Store on my Chromebook. I've gone into settings and turned off the "Google Play Store" option, and I've even restarted the device multiple times. Despite this, I'm still seeing these 100.115.x.x IPs when I check my network configuration.

 

I've tried the following:

  • Disabling the Google Play Store through settings.
  • Restarting my Chromebook.
  • Checking for and installing any available Chrome OS updates.
  • Power washed the Chromebook

 

None of these actions have resolved the issue. The 100.115.x.x IPs continue to appear.

 

I understand that ARC is responsible for these addresses, but I'm unsure why they're still present after disabling Android app functionality.

Has anyone else experienced this issue? Does anyone have any suggestions on how to completely remove or disable ARC and prevent these IPs from appearing? Any help would be greatly appreciated.

 

The odd thing is.... when i go on the chromebook and type chrome://Policy i can see that ARC is disabled!

 

NOTE to ADMINS: Any chance we could have a Chromebook/ChromeOS subsection in the main OS section of the forum please?

 

Thanks in advance!

Edited by Jaan
  • Like 1
Posted

We're experiencing issues with our web filter blocking traffic from Chromebooks.

 

The filter is identifying the source IP as 100.115.x.x, which I believe is related to the Android Runtime for Chrome OS (ARC). This range seems to be used for internal communication between the Android VM/sandbox and the Chromebook's host system.

 

Consequently, the web filter isn't seeing the actual DHCP-assigned IP address of the Chromebook, which is necessary for our filtering policies to work correctly.

 

We previously used Android apps on our Chromebooks, which required ARC to be enabled. However, we no longer use those apps, and ARC is now disabled. Despite this, the 100.115.x.x IP range is still appearing in our network traffic.

 

So i'm somewhat confused.

Posted

Currently trialing Securly, and just switched to the Extension method which works better and has more features. We're not having any filtering issues as such now.....just a visual annoyance. 

 

cheers

Posted

Ok,  my securly also shows that range as internal IP,  I assume it has to do with the way the extension works.  I think it is an internal securly IP rather than an IP associated to your Chromebook. 

Posted

I don't see that  IP in any other system other than on the Securly, so I assumed it was a securly issue.  Never really needed to use the internal IP from securly so it hasn't bothered me.  I might stick a ticket into support and see what they say. I only use it on the Chromebooks, use our Fortigate on the windows devices.

Posted (edited)

It doesn't seem to be causing any issues, just not what i was expecting nor do i understand it.

Edited by Jaan

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...