anatol · GitHub

systemd version the issue has been seen with
246.6 at Arch Linux

Used distribution
Arch Linux, up-to-date

Linux kernel version used (uname -a)
5.9.3-arch1-1

CPU architecture issue was seen on
x86_64

My company recently moved to PulseSecure VPN. It provides proprietary closed-source client that sets up a VPN connection. Some people use this tool at Fedora with NetworkManager and say the tools works fine.

I am trying to use it at Arch with systemd-network and systemd-resolved. The tool seems sets up a VPN connection. But it does not configure DNS routing correctly. So I have to configure DNS manually like this:

$ cat /etc/systemd/resolved.conf.d/mycompany.conf
[Resolve]
DNS=162.200.100.12
Domains=mycompany.corp mycompany.com net.mycompany.net local.mycompany.com mycompany.biz
LLMNR=no

and then sudo systemctl restart systemd-resolved.service. i.e. the DNS configuration and service restart has to be done manually. I would love to find a better automatic way to configure DNS at the VPN connection event.

Taking into account that some folks were able to make it working with NetworkManager flawlessly I believe that pulsesecure UI tool tries to send this DNS information to the system but systemd-resolved does not receive this information for some reason. I am looking for a way to make systemd-resolved with pulseUI without manual intervention.

I am eager to provide you as much debug information as possible but I do not know where to start debugging this issue.

Read the original on github.com ↗