NetworkManager does not use openconnect GlobalProtect VPN's DNS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openconnect (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1. Add a GlobalProtect VPN in network settings GUI, set DNS to manual, enter DNS IP address.
2. Open an internal website that should be routed through the VPN.
Actual: failed to open the internal website.
Expected: should open the internal website.
Content of `/etc/resolv.conf`: using systemd-resolved's 127.0.0.53.
Output of `resolvectl status`: only wlo1 has DNS Servers entry, there is no DNS Servers entry in vpn0.
Workaround: manually set the DNS in /etc/resolv.conf. Side effects of the workaround: the setting does not persist.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openconnect 8.05-1
ProcVersionSign
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 8 13:35:21 2021
InstallationDate: Installed on 2021-06-05 (33 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: openconnect
UpgradeStatus: No upgrade log present (probably fresh install)
What does "nmcli con show" say for the offending connection? Does NM know the DNS server? Is this just a case of Ubuntu's NM not working correctly with its systemd DNS setup?
If you connect with openconnect on the command line and add the `-v` option, do you see DNS servers? I have a feeling Ubuntu's vpnc-script may not be working correctly for DNS either, so I'm less interested in whether it *works* and asking for the debug output.