This is to consolidate the necessary changes after installing this package.
Upgrading from 10.3.5_36-1 or earlier — three one-time steps
-
If the upgrade fails with
/usr/bin/resolvconf exists in filesystem, that symlink was created by the old package (or by SonicWall'sinstall.sh) and is not owned by anything. Remove it and retry:sudo rm /usr/bin/resolvconfThe package now depends on
resolvconfinstead of forging that symlink, so pacman will ask which provider to install. Picksystemd-resolvconfif you usesystemd-resolved,openresolvotherwise. -
NEService.servicemoved from/etc/systemd/systemto/usr/lib/systemd/system, where packaged units belong. If you had enabled it, the old symlink now dangles and the daemon will not start at boot — refresh it:sudo systemctl reenable NEService.service -
pppdis no longer involved (10.3.x speaks PPP itself over/dev/net/tun), so the setuid bit from the previous instructions can be reverted:sudo chmod u-s /usr/bin/pppd
After installing
-
Enable and start the NEService daemon:
sudo systemctl enable --now NEService.service -
DNS during the session: NetExtender hands its nameservers to
resolvconfon connect and withdraws them on disconnect. Withsystemd-resolvconfthat goes intosystemd-resolvedrather than rewriting the file, so/etc/resolv.confshould point at one of resolved's files:sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
Do note the DNS resolution depends on the servers received by NetExtender, and thus may not allow resolving external hostnames, or hostnames in your local network. If you experience DNS failures, add fallback nameservers to /etc/systemd/resolved.conf under [Resolve]
FallbackDNS=1.1.1.1 8.8.8.8
Then restart: sudo systemctl restart systemd-resolved
Pinned Comments
satoki commented on 2026-06-18 21:26 (UTC) (edited on 2026-08-27 23:43 (UTC) by satoki)
This is to consolidate the necessary changes after installing this package.
Upgrading from 10.3.5_36-1 or earlier — three one-time steps
If the upgrade fails with
/usr/bin/resolvconf exists in filesystem, that symlink was created by the old package (or by SonicWall'sinstall.sh) and is not owned by anything. Remove it and retry:sudo rm /usr/bin/resolvconfThe package now depends on
resolvconfinstead of forging that symlink, so pacman will ask which provider to install. Picksystemd-resolvconfif you usesystemd-resolved,openresolvotherwise.NEService.servicemoved from/etc/systemd/systemto/usr/lib/systemd/system, where packaged units belong. If you had enabled it, the old symlink now dangles and the daemon will not start at boot — refresh it:sudo systemctl reenable NEService.servicepppdis no longer involved (10.3.x speaks PPP itself over/dev/net/tun), so the setuid bit from the previous instructions can be reverted:sudo chmod u-s /usr/bin/pppdAfter installing
Enable and start the NEService daemon:
sudo systemctl enable --now NEService.serviceDNS during the session: NetExtender hands its nameservers to
resolvconfon connect and withdraws them on disconnect. Withsystemd-resolvconfthat goes intosystemd-resolvedrather than rewriting the file, so/etc/resolv.confshould point at one of resolved's files:sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.confDo note the DNS resolution depends on the servers received by NetExtender, and thus may not allow resolving external hostnames, or hostnames in your local network. If you experience DNS failures, add fallback nameservers to
/etc/systemd/resolved.confunder[Resolve]Then restart:
sudo systemctl restart systemd-resolved