Unable to access any subdomain provided by VPN provider until reboot.

Status changed to 'Confirmed' because the bug affects multiple users.

The problem occurs when I use network-manager to initiate the VPN.

The problem does not occur when I run openconnect from the command line:

sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper https://vpn.myschool.edu

I have figured this out as well. It would be nice to be able to use
gnome-network-manager though.

On Jan 9, 2018 18:25, "mash" <email address hidden> wrote:

> The problem occurs when I use network-manager to initiate the VPN.
>
>
> The problem does not occur when I run openconnect from the command line:
>
> sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
> https://vpn.myschool.edu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735798
>
> Title:
> Unable to access any subdomain provided by VPN provider until reboot.
>
> Status in network-manager package in Ubuntu:
> Confirmed
> Status in openconnect package in Ubuntu:
> Confirmed
>
> Bug description:
> After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
> and any domain hosted by the server. For reference, this is my
> school's VPN, and I am unable to get on mygateway or even the school's
> main website after I disconnect from the VPN or the computer sleeps
> after the VPN has been started. It uses EAP authentication.
>
> Here is the log after connecting once, turning off, and restarting:
> LOG:
> POST https://vpn.myschool.edu/
> getaddrinfo failed for host 'vpn.myschool.edu': Name or service not
> known
> Failed to open HTTPS connection to vpn.myschool.edu
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: network-manager 1.8.4-1ubuntu3
> ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
> Uname: Linux 4.13.0-17-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.5
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Dec 1 11:39:56 2017
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> InstallationDate: Installed on 2016-12-02 (364 days ago)
> InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
> IpRoute:
> default via 192.168.1.1 dev wlp5s0 proto static metric 600
> 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
> 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144
> metric 600
> 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
> NetworkManager.state:
> [main]
> NetworkingEnabled=true
> WirelessEnabled=true
> WWANEnabled=true
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
> nmcli-nm:
> RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING
> WIFI-HW WIFI WWAN-HW WWAN
> running 1.8.4 connected started full enabled
> enabled enabled enabled enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+
> subscriptions
>