Native L2TP/IPSec VPN client connects but does not tunnel/redirect network traffic
Reported by
markh...@gmail.com,
Aug 12
|
||
Issue description
Chrome Version: 68.0.3440.75
Chrome OS Version: 10718.63.0
Chrome OS Platform: Acer C720 (Peppy)
Network info: Wi-Fi, WPA, Linksys WRT1900ACS
Please specify Cr-* of the system to which this bug/feature applies (add
the label below).
Steps To Reproduce:
(1) Set up and connect to L2TP/IPSec VPN
(2) Check public IP address using "what's my IP"-type website
(3)
Expected Result: VPN client connects. IP address of VPN server is now public IP address.
Actual Result: VPN client connects. Local ISP IP address is still public IP address.
How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?) Always
What is the impact to the user, and is there a workaround? If so, what is
it?
As Chromebook VPN client does connect to VPN server, it gives user false impression of VPN protection.
Please provide any additional information below. Attach a screen shot or
log if possible.
There is a work-around: After connecting to local Wi-Fi hotspot, "forget" the connection. Then reconnect. VPN now works correctly. I have not tested whether or not this "fix" is persistent.
This thread also explains problem and work-around: https://productforums.google.com/forum/#!topic/pixelbook/lTKJXKBQV88
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
,
Aug 18
"Wi-Fi forget" fix still persistent after latest ChromeOS update to Version 69.0.3497.35 (Official Build) beta (64-bit).
,
Jan 15
|
||
►
Sign in to add a comment |
||
Comment 1 by dtapu...@chromium.org
, Aug 14