[Bug 2067897] Re: Ubuntu 24.04 does not install resolvconf uses systemd-resolved instead which is broken
John Orr
2067897 at bugs.launchpad.net
Fri Jun 7 01:01:41 UTC 2024
FYI - Tobias wasn't keen on the dummy interface option, per his response here
https://github.com/strongswan/strongswan/discussions/2085#discussioncomment-9678750
(though maybe that is a good option, but dnsmasq needs to be changed to suit it?)
I also hit a problem where a server I wish to access over the VPN also
has an IP address on the public internet - and whereas with the old
resolvconf executable, somehow starting the VPN used to automatically
switch me to using the VPN version of that server, using a dummy
interface this didn't happen - it kept using the public ip address for
this server. By setting iface in /etc/strongswan.d/charon/resolve.conf
to my ethernet interface, it replaced the public DNS (1.1.1.1) on that
interface with my VPN DNS servers, so things worked. Unfortunately,
when the VPN went down, it didn't restore 1.1.1.1 (and I'd hoped might
be possible with the resolvectl "revert" command - alas no) - it just
removed all DNS on that link.
I've almost zero knowledge in this space compared to Tobias, Lennart,
etc - but it certainly feels like stuff that just worked with the old
resolvconf has become quite the headache now - even if the new
resolvectl resolvconf is better for a bunch of other reasons.
--
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/2067897
Title:
Ubuntu 24.04 does not install resolvconf uses systemd-resolved instead
which is broken
Status in systemd package in Ubuntu:
Confirmed
Bug description:
# lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04 LTS
Release: 24.04
# dpkg --status systemd
Package: systemd
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 11728
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Architecture: amd64
Multi-Arch: foreign
Version: 255.4-1ubuntu8
# dpkg --status systemd-resolved
Package: systemd-resolved
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 884
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Architecture: amd64
Multi-Arch: foreign
Source: systemd
Version: 255.4-1ubuntu8
Replaces: resolvconf, systemd (<< 251.3-2~)
Provides: resolvconf
WHAT HAPPENS:
# /sbin/resolvconf -a lo.ipsec
Dropped protocol specifier '.ipsec' from 'lo.ipsec'. Using 'lo' (ifindex=1).
nameserver 8.8.8.8
Failed to set DNS configuration: Unit dbus-org.freedesktop.network1.service not found.
background, using strongswan vpn (swanctl) the error:
installing DNS server 192.168.170.10 via resolvconf
2024-06-03T12:22:51.802864+02:00 tester213 charon-systemd[3121]: resolvconf: Dropped protocol specifier '.ipsec' from 'lo.ipsec'. Using 'lo' (ifindex=1).
2024-06-03T12:22:51.809365+02:00 tester213 dbus-daemon[714]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.service' requested by ':1.115' (uid=0 pid=3161 comm="/sbin/resolvconf -a lo.ipsec" label="unconfined")
2024-06-03T12:22:51.809660+02:00 tester213 dbus-daemon[714]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.network1.service': Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.810206+02:00 tester213 charon-systemd[3121]: resolvconf: Failed to set DNS configuration: Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.811158+02:00 tester213 charon-systemd[3121]: adding DNS server failed
2024-06-03T12:22:51.811282+02:00 tester213 charon-systemd[3121]: installing DNS server 192.168.170.10 via resolvconf
2024-06-03T12:22:51.828246+02:00 tester213 charon-systemd[3121]: resolvconf: Dropped protocol specifier '.ipsec' from 'lo.ipsec'. Using 'lo' (ifindex=1).
2024-06-03T12:22:51.830988+02:00 tester213 dbus-daemon[714]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.service' requested by ':1.116' (uid=0 pid=3165 comm="/sbin/resolvconf -a lo.ipsec" label="unconfined")
2024-06-03T12:22:51.831891+02:00 tester213 dbus-daemon[714]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.network1.service': Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.833400+02:00 tester213 charon-systemd[3121]: resolvconf: Failed to set DNS configuration: Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.836087+02:00 tester213 charon-systemd[3121]: adding DNS server failed
2024-06-03T12:22:51.836233+02:00 tester213 charon-systemd[3121]: handling INTERNAL_IP4_DNS attribute failed
2024-06-03T12:22:51.836297+02:00 tester213 charon-systemd[3121]: installing DNS server 192.168.170.10 via resolvconf
2024-06-03T12:22:51.852643+02:00 tester213 charon-systemd[3121]: resolvconf: Dropped protocol specifier '.ipsec' from 'lo.ipsec'. Using 'lo' (ifindex=1).
2024-06-03T12:22:51.854550+02:00 tester213 dbus-daemon[714]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.service' requested by ':1.117' (uid=0 pid=3169 comm="/sbin/resolvconf -a lo.ipsec" label="unconfined")
2024-06-03T12:22:51.854995+02:00 tester213 dbus-daemon[714]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.network1.service': Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.855363+02:00 tester213 charon-systemd[3121]: resolvconf: Failed to set DNS configuration: Unit dbus-org.freedesktop.network1.service not found.
2024-06-03T12:22:51.856505+02:00 tester213 charon-systemd[3121]: adding DNS server failed
2024-06-03T12:22:51.857409+02:00 tester213 charon-systemd[3121]: handling INTERNAL_IP4_DNS attribute failed
WHAT SHOULD HAPPEN : the vpn dns server should be added without an
error
why can`t I install plain resolvconf which was working perfectly fine in Ubuntu 22.04 (tried to use the binary of 2204, the issue persists, the culprit is systemd in 2404)?
24.04 forces me to use systemd-resolved which does not work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067897/+subscriptions
More information about the foundations-bugs
mailing list