> Ubuntu 24.04 does not install resolvconf uses systemd-resolved instead
which is broken
Clickbait bug titles like this do not usually inspire confidence.
Marking as "opinion" helps my triage process, because I do my best to
focus on actionable items, and cannot always spend time "defending" the
default configurations of systemd and Ubuntu.
Looking closer at the bug, I see that you are having difficulty
configuring DNS via strongswan. The problem is that by default, the
strongswan resolve plugin uses the lo interface to set DNS servers on.
But, systemd-resolved does allow setting DNS on loopback interfaces.
This leads to the fallback attempt via systemd-networkd, but assuming
this is a desktop, I would not expect systemd-networkd to be running
(NetworkManager is the default on desktop).
Anyways, you can change the default interface used by the resolve plugin
using the following snippet (or modifying
/etc/strongswan.d/charon/resolve.conf directly):
# /etc/strongswan.d/charon/resolve-iface.conf
resolve {
load = yes
resolvconf {
# Interface name/protocol sent to resolvconf(8).
iface = <your interface name here>.ipsec
}
}
That should fix the problem.
> if so, wow I am impressed how ignorant one can be..
This sort of comment does not make me want to work with you in the
future.
** Changed in: systemd (Ubuntu)
Status: Opinion => Incomplete
** Also affects: strongswan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 strongswan package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
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-disc...@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-disc...@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/strongswan/+bug/2067897/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
