[Bug 2013072] Re: Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn mess with /etc/resolv.conf

[Nick Rosbrook]

This is done in the systemd-resolved package, which exists in Kinetic
and newer (previously systemd-resolved components were shipped in the
main systemd package).

However, I don't think this is something that we will SRU to Jammy or
Focal.

** Changed in: systemd (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2013072

Title:
  Missing symlink /sbin/resolvconf -> /bin/resolvectl makes openfortivpn
  mess with /etc/resolv.conf

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In jammy (22.04) and focal (20.04) the executable /usr/bin/resolvectl
  is provided by the package "systemd". If you install the packages
  libnss-resolve and openfortivpn and run "openfortivpn vpn.example.com
  -u user -v" you get undesired behavior:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to modify /etc/resolv.conf directly.
  DEBUG:  Adding "nameserver 10.10.10.10", to /etc/resolv.conf.
  DEBUG:  Adding "search ~10.in-addr.arpa ~example.com", to /etc/resolv.conf.
  [...]

  resolvectl can emulate the behavior of resolvconf so if you create a
  symbolic link "sudo ln -s /usr/bin/resolvectl /sbin/resolvconf" then
  openfortivpn happily uses resolvconf instead of messing with
  /etc/resolv.conf:

  [...]
  INFO:   Adding VPN nameservers...
  DEBUG:  Attempting to run /sbin/resolvconf.
  DEBUG:  resolvconf_call: /sbin/resolvconf -a "ppp0.openfortivpn"
  [...]

  So it would be great if the symlink could be included in the package
  "systemd". Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2013072/+subscriptions