Hello, I have an issue with netextender where it doesn't play nice with /etc/resolv.conf
, when it is managed by systemd-resolved
.
The latter package requires that /etc/resolv.conf
is a symlink to /run/systemd/resolve/resolv.conf
. However, when netextender connects to my VPN, it will overwrite /etc/resolv.conf
and replace it with a standalone file. After disconnecting from the VPN, sometimes a static version of /etc/resolv.conf
remains, and systemd-resolved
doesn't work to resolve .local mDNS addresses. (Typically, I've just tested now, and the symlink was restored, but it contained the additional nameservers and search domains for my VPN, so DNS stopped working).
This is a bit of a nuisance, as the company domain ends in .local, which conflicts with mDNS of course, and when systemd-resolved is not managing DNS lookups, mDNS doesn't work on my LAN, and I can't cast any audio or video to my chromecast(s). I've wasted much time trying to figure out why I was unable to cast A/V from my PC, and I've pinned it down to the SSL VPN messing around with /etc/resolv.conf
.
Has anyone else come across this issue and have any suggestions for making netextender (or is it pppd?) play nicer with systemd-resolved? I'll probably open a support ticket with SonicWall on this, would that be the best place to report this?
Thanks and kind regards, Alex
Pinned Comments
physkets commented on 2021-02-10 15:33 (UTC)
In case of changes/updates to
ppp
, you will need to re-runchmod -v u+s /usr/sbin/pppd
.