FS#68862 - [systemd] systemd-networkd is not getting default route from DHCP

Attached to Project: Arch Linux
Opened by Vadim (VadimD) - Sunday, 06 December 2020, 01:33 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 09 December 2020, 19:47 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I have a very simple network file:

$ cat /etc/systemd/network/ens3.network
[Match]
Name=ens3

[Network]
DHCP=ipv4

On systemd version 246.4-1 I get both IP address and default route:

$ ip r
default via 172.31.1.1 dev ens3 proto dhcp src 88.99.85.67 metric 1024
172.31.1.1 dev ens3 proto dhcp scope link src 88.99.85.67 metric 1024

$ ip a show dev ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:54:a2:01:ad:1e brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet 88.99.85.67/32 scope global dynamic ens3
valid_lft 86392sec preferred_lft 86392sec
inet6 fe80::5054:a2ff:fe01:ad1e/64 scope link
valid_lft forever preferred_lft forever

But with systemd version 247.1-1 I only get ip address and no routes:

$ ip r
$ ip a show dev ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:54:a2:01:ad:1e brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet 88.99.85.67/32 scope global dynamic ens3
valid_lft 86315sec preferred_lft 86315sec
inet6 fe80::5054:a2ff:fe01:ad1e/64 scope link
valid_lft forever preferred_lft forever


This is a remote vps so I lost my connection after update because of this. Downgrading back to 246.4-1 fixes the issue.
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 09 December 2020, 19:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 247.1-3
Comment by Vadim (VadimD) - Sunday, 06 December 2020, 01:42 GMT
It seems this was already fixed https://github.com/systemd/systemd/issues/17803
Comment by RK (keoz) - Sunday, 06 December 2020, 22:58 GMT
I have exactly the same problem. I could resolve this only by downgrading to 246.4-1 (or using some other network management system).

Also on a VPS.
Comment by Silvan (silvan) - Wednesday, 09 December 2020, 16:53 GMT
This Bug was resolved with systemd 247.1-3.

Loading...