Public bug reported: [What I expected to happen] openconnect (command line) and network-manager-openconnect-gnome behave in the same way when it comes to resolving hosts through the vpn
[What happened] openconnect from the command line sets up the system in a way that can resolve hosts through the vpn. network-manager-openconnect-gnome does not set up the system in a way that can resolve hosts through the vpn. [Steps to reproduce] This seems to be a new issue with network-manager-openconect-gnome in Ubuntu 18.04+ I install sudo apt install network-manager-openconnect-gnome to get gnome integration with opeconnect and Cisco AnyConnect Compatible VPN (openconnect) As an aside (which may actually be relevant) I do this to get *.local addresses to resolve: sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf as per systemd docs Move dns before mdns4_minimal in /etc/nsswitch.conf If I connect to the VPN with openconnect through the gnome network manager, VPN addresses (sites for work) do not resolve. Regular sites continue to work as expected. If I connect to the VPN with openconnect on the command line with sudo openconnect vpn.mycompany.com, VPN addresses (sites for work) do resolve. Regular sites continue to work as expected. I thought I would check to see if there were any differences between /etc/resolv.conf with each of these VPN connection methods and sure enough, there is one: openconnect on the command line (working): #@VPNC_GENERATED@ -- this file is generated by vpnc # and will be overwritten by vpnc # as long as the above mark is intact # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 10.10.10.10 nameserver 10.10.10.11 search broadband mycompany.com openconnect gnome integration (not working): # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 192.168.1.1 nameserver 10.10.10.10 nameserver 10.10.10.11 search broadband mycompany.com If I remove (or comment out) the nameserver 192.168.1.1, which is the difference in content between the working and not working files... everything works as expected. I can resolve addresses within the company and regular sites work as expected. This does not happen with Fedora. Everything works out of the box. I'm not sure why the network-manager-openconnect-gnome package works differently or if there's a way I can make it work without either Editing the file by hand. Using the openconnect tool from the command line and keeping a terminal open running that command. [System details] lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy network-manager-openconnect-gnome network-manager-openconnect-gnome: Installed: 1.2.4-1ubuntu1 Candidate: 1.2.4-1ubuntu1 Version table: *** 1.2.4-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 1.2.4-1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: network-manager-openconnect (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854205 Title: nameservers update differently with openconnect and openconnect-gnome in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1854205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs