[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Sorry, Eoan is EOL in just a few weeks, and I don't think this will make it. please upgrade to Focal if still affected by this bug. ** Changed in: systemd (Ubuntu Eoan) Status: New => Won't Fix -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Won't Fix Status in systemd source package in Focal: Fix Released Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
thanks, per comment 12 marking fixed in focal. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Focal) Assignee: Dan Streetman (ddstreet) => (unassigned) -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: Fix Released Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Tried with image ubuntu-minimal-2004-focal-v20200501 (systemd 245.4-4ubuntu3). No issues seen. I will then upgrade our project to Focal, which also has LTS. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: In Progress Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
> 245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be fine: ah, that's excellent, then, I'll try to find the upstream patch fixing this. ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: In Progress Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
I marked this as affecting Eoan, but I may not be able to get to patching it before it reaches EOL, since that's in just 2 months. If you do happen to upgrade to Focal, and find it's fixed there, please add a comment. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: In Progress Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Also I marked this as fix released upstream (per comment 8), and assume this is fixed for Groovy as well (or, will be fixed during Groovy dev cycle), but I did not specifically check Groovy. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: In Progress Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be fine: May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): REQUEST (renewing) May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): lease expires in 23h 59min 57s May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 expires in 20h 59min 57s May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 expires in 11h 59min 59s May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Remembering updated address: 10.164.0.2/32 (valid for 1d) May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: main, proto: dhcp, type: unicast May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, proto: dhcp, type: unicast May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): REQUEST (renewing) May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): lease expires in 23h 59min 57s May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 expires in 20h 59min 58s May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 expires in 11h 59min 59s May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Remembering updated address: 10.164.0.2/32 (valid for 1d) May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: main, proto: dhcp, type: unicast May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, proto: dhcp, type: unicast -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1,
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
For testing with the latest upstream, can you try the systemd from this ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd-upstream You should only use that for testing, please - remove it and revert the packages back to the official versions once you've tested. Also, strictly as a workaround, you could try setting the mtu with a link file, like: [Match] Name=ens4 [Link] MTUBytes=1460 see 'man systemd.link' for more details, and of course that doesn't actually fix the problem, just tries to work around it by setting your link mtu before running dhcp, so your 'original' link mtu == dhcp mtu. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src:
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Do you have any suggestion on what to look at? Systemd only tracks bugs for the two most recently released versions (which should be 245 and 244) and I don't have the ressources to test those. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume this is a regression, potentially from
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
it looks like your dhcp lease is expiring, which causes networkd to drop your dhcp configuration, including resetting your mtu back to its original value. That's done asynchronously by netlink, and networkd sets a flag "setting_mtu" while the netlink request to change the mtu is pending. However, immediately after your lease is lost, you regain it, and networkd begins setting up the interface with the dhcp info, including the mtu. Unfortunately, since the mtu reset hasn't completed yet, "setting_mtu" flag is still set, and the call to link_set_mtu() returns silently without actually changing the mtu. At least that's what seems like is happening in your case. It's unusual to lose your dhcp lease before renewing it, so you may be able to look at why that's happening to avoid this (hopefully that's not a separate bug in systemd...), but re: the failure to set mtu, I believe that's going to be a problem that still exists upstream, so resolving this bug will need fixing upstream first. If you (or anyone else) has time to open a bug upstream for this (preferably, after testing with upstream systemd to verify it's still a bug upstream), please add a note to this bug. -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst:
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
After the weekend, I observed that the original MTU gets set on every second renew: Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 23 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 Apr 24 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 24 21:50:58 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 Apr 25 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 25 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 Apr 26 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460 Apr 26 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420 -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4:
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
This is the full log: Apr 23 09:51:00 ct-prod systemd[1]: Stopping Network Service... Apr 23 09:51:00 ct-prod systemd[1]: systemd-networkd.service: Succeeded. Apr 23 09:51:00 ct-prod systemd[1]: Stopped Network Service. Apr 23 09:51:00 ct-prod systemd[1]: Starting Network Service... Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing state UNSET → OPENING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing state OPENING → AUTHENTICATING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of '/etc/systemd/network' changed Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of '/run/systemd/network' changed Apr 23 09:51:00 ct-prod systemd-networkd[1737]: No virtualization found in DMI Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Virtualization found, CPUID=KVMKVMKVM Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Found VM virtualization kvm Apr 23 09:51:00 ct-prod systemd-networkd[1737]: /usr/lib/systemd/network/80-container-host0.network: Conditions in the file do not match the system environment, skipping. Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Link 18378 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Link 18376 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Link 18374 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Link 18372 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Flags change: +UP +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Link 3 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Saved original MTU: 1500 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Link 2 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: New device has no master, continuing without Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Link 1 added Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: udev initialized link Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Saved original MTU: 65536 Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Adding address: fe80::c0e2:b6ff:fec5:c370/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Adding address: fe80::bc1c:baff:fedf:f0ef/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Adding address: fe80::d84f:edff:fe33:55a0/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Adding address: fe80::42:45ff:fed1:a3c2/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Gained IPv6LL Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Gained IPv6LL Apr 23 09:51:00 ct-prod
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
> 09:51:00 ens4: Configured > 21:50:59 ens4: DHCP lease lost er, did you happen to trim a few lines between those? Can you please provide the full unedited log? -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume this is a regression, potentially from https://github.com/systemd/systemd/issues/12552 or
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Confirmed Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume this is a regression, potentially from https://github.com/systemd/systemd/issues/12552 or
