New issue
Advanced search Search tips

Issue 813424 link

Starred by 5 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

VPN not working

Reported by carajayn...@gmail.com, Feb 18 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.30.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.65 Safari/537.36
Platform: 10323.30.0 (Official Build) beta-channel cave

Example URL:

Steps to reproduce the problem:
1. Turn on chosen VPN service (either through Android app with #arc-vpn flag enabled, or through the manual ChromeOS VPN) 
2. It says that connection to the VPN has been successfully established (with either above method of connecting)

What is the expected behavior?
I haven't tried using an Android app to setup a VPN connection before, but thought I'd try as supposedly the #arc-vpn flag allows an Android VPN app to work for both Android apps and default Chrome apps/windows. With this enabled I haven't been able to successfully establish a VPN connection. 

Before trying this I could connect to a VPN by setting up servers manually in my device's default VPN settings.

What went wrong?
I have a working internet connection and haven't lost any functionality on my Chromebook, but there I'm not actually connected to a VPN despite it saying I have established a VPN connection, and my internet traffic is still detected as VPN-less.

Did this work before? N/A 

Chrome version: 65.0.3325.65  Channel: beta
OS Version: 10323.30.0
Flash Version: 28.0.0.161
 
Should probably add that disabling the #arc-vpn flag and restarting the device doesn't fix the issue.

Comment 2 by mmenke@chromium.org, Feb 20 2018

Components: -Internals>Network Internals>Network>VPN
This is also occurring for my manually set up VPN connections, not using ARC. They appear to have connected but traffic is not using the VPN.
Meant to add:
oogle Chrome	64.0.3282.144 (Official Build) (64-bit)
Revision	0
Platform	10176.68.0 (Official Build) stable-channel clapper
Firmware Version	Google_Clapper.5216.199.7

The issue started occurring with the last update a couple of days ago.
Some further digging makes me think this might be a routing issue:-

This is the routing table without a VPN connection:
crosh> route
/0 default via 192.168.1.1 dev wlan0 metric 1 
/1 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.101 
/2 

And then with the VPN connected:
crosh> route
/0 default via 192.168.1.1 dev wlan0 metric 1 
/1 10.42.44.0/22 dev tun0 proto kernel scope link src 10.42.44.26 
/2 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.101 

Labels: Enterprise-Triaged

Sign in to add a comment