Hi Pedro,
Can you please try this with the latest version of systemd? We have
249.11-0ubuntu3.9 which has a patch for a similar sounding bug (I don't
*think* it's the same thing, but just to be sure).
Assuming that does not resolve the issue, can you please provide debug-
level logs from systemd-networkd during a span where the routes would be
created? You can enable debug logging by doing:
$ mkdir -p /etc/systemd/system/systemd-networkd.service.d
$ cat > /etc/systemd/system/systemd-networkd.service.d << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
$ systemctl daemon-reload
$ systemctl restart systemd-networkd
Then grab some logs from an appropriate timespan. I think networkctl
forcerenew should do the trick:
$ networkctl forcerenew
$ journalctl -u systemd-networkd --since "5min ago" > logs.txt
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
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/2009743
Title:
networkd: classless routes served by DHCP are created incorrectly
Status in systemd package in Ubuntu:
Incomplete
Bug description:
After upgrading 20.04 systems to 22.04, the classless routes served
via DHCP are not being registered correctly - they are missing the
gateway address.
Expected routes - these are taken from a 20.04 system on the same
network:
$ ip route
default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
Actual routes - these are the routes created in one of the affected
22.04 systems:
$ ip route
default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via"
gateway address, and therefore don't work.
(For some reason there are also static routes created for DNS server
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but
harmless.)
Both the working and non-working systems are being managed by netplan.
The non-working system has a bonded interface but I have checked that
is not the cause of the problem - using a physical interface directly
has the same result.
I have attached the files /etc/netplan/00-installer-config.yaml and
/run/systemd/network/10-netplan-bond0.network of the affected system.
Affected system:
Ubuntu version: Ubuntu 22.04.2 LTS
systemd version: 249.11-0ubuntu3.6
Older system not affected:
Ubuntu version: Ubuntu 20.04.5 LTS
systemd version: 245.4-4ubuntu3.19
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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
