New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 838915 link

Starred by 8 users

Issue metadata

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



Sign in to add a comment

Network speeds dramatically throttled when connected to OpenVPN full tunneling connection

Reported by jeremy.l...@warbyparker.com, May 2 2018

Issue description

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

Example URL:

Steps to reproduce the problem:
1. Configure an OpenVPN client configuration on ChromeOS
2. Connect to OpenVPN server
3. Run a speedtest
4. Disconnect from OpenVPN session
5. Re-run speedtest
6. Bandwidth speeds are reduced by up to 75% on OpenVPN session

What is the expected behavior?
minimal impact to bandwidth.

What went wrong?
Not sure how long this has been an issue, but we noticed it with our fleet of mobile, WFH users on ChromeOS running at 64.x and following.  This issue occurred about a year ago on previous versions of ChromeOS.  The issue at that time was a bug with the virtual interface (TUN1) created for the OpenVPN session.  The bug was resolved in a CHromeOS version release.

Did this work before? Yes Not certain - but probably 63.x

Chrome version: 66.0.3359.137  Channel: beta
OS Version: 10452.74.0
Flash Version: 29.0.0.140
 
Components: -Internals>Network Internals>Network>VPN
Is this with the built-in Chrome OS OpenVPN client or a separately installed OpenVPN app?
Cc: ofodile@google.com tharu@chromium.org
Owner: abhishekbh@chromium.org
Correction on this ticket - our OpenVPN is an SSL configuration, not an L2TP.
Labels: Hotlist-Enterprise
Cc: kathrelk...@chromium.org
[Has anyone in Google able to repro this yet ?]
We spent a few months troubleshooting this with Google. Ticket #587053
Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment