New issue
Advanced search Search tips

Issue 924205 link

Starred by 9 users

Issue metadata

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



Sign in to add a comment

DNS Failing on L2TP-IPsec VPN or AnyConnect VPN

Reported by m...@duosecurity.com, Today (11 hours ago)

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11578.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3669.0 Safari/537.36
Platform: 11578.0.0 (Official Build) dev-channel eve

Example URL:

Steps to reproduce the problem:
1. Have a pixelbook on 72.0.3626.59 with a working VPN configuration (L2TP-IPsec or Anyconnect 4.6.02078 Android app)
2. switch chromeos release channel from beta to dev 73.0.3669.0
3. Connect either VPN successfully then try to browse resources or run the Chrome Connectivity Diagnostics App

What is the expected behavior?
Fully functioning VPN

What went wrong?
It seems as if there may be a problem with the dev lo 127.0.0.1 interface (see attached screenshots)
dns does not resolve and returns problem status code -137

Did this work before? Yes 72.0.3626.59

Chrome version: 73.0.3669.0  Channel: dev
OS Version: 11578.0.0
Flash Version: 

Thanks in advance!
 
Screenshot 2019-01-22 at 12.06.34 PM.png
312 KB View Download
Screenshot 2019-01-22 at 1.13.30 PM.png
131 KB View Download

Comment 1 by ericorth@chromium.org, Today (10 hours ago)

Components: -Internals>Network Internals>Network>VPN
-137 indicates some sort of system error when requesting DNS through getaddrinfo().

If that is breaking dependent on Chrome version, appears to be something with the VPN connection.  Moving this to the VPN subcomponent.

Sign in to add a comment