[Touch-packages] [Bug 1839231] Re: updating bionic to 237-3ubuntu10.25 restarts systemd-networkd
Thanks! This system is using netplan, with ipv6-privacy enabled in netplan (subsequent to the fix in bug #1750392): root@pentos:~# cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: ens5: dhcp4: true ipv6-privacy: true The issue reproduces with the ens5 interface. Stopping systemd-networkd does not change any addresses, but starting it again removes all the "deprecated" addresses, even if they are in use by TCP connections: root@pentos:~# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether [mac-redacted] brd ff:ff:ff:ff:ff:ff inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic ens5 valid_lft 52839sec preferred_lft 52839sec inet6 [redacted-ipv6-/64]:8d03:bfce:131d:190/64 scope global temporary dynamic valid_lft 596sec preferred_lft 596sec inet6 [redacted-ipv6-/64]:306e:2bf2:9d28:ef32/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:c060:f52:5638:10e9/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:d941:e7ff:cc75:9968/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:2dae:1ae3:c572:ed57/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:90ec:5051:54de:f345/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:5497:3bdc:6452:c67f/64 scope global temporary deprecated dynamic valid_lft 596sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:[slaac-redacted]/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 596sec preferred_lft 596sec inet6 fe80::[ll-redacted]/64 scope link valid_lft forever preferred_lft forever root@pentos:~# systemctl stop systemd-networkd root@pentos:~# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether [mac-redacted] brd ff:ff:ff:ff:ff:ff inet 192.168.1.103/24 brd 192.168.1.255 scope global dynamic ens5 valid_lft 52794sec preferred_lft 52794sec inet6 [redacted-ipv6-/64]:8d03:bfce:131d:190/64 scope global temporary dynamic valid_lft 587sec preferred_lft 587sec inet6 [redacted-ipv6-/64]:306e:2bf2:9d28:ef32/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:c060:f52:5638:10e9/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:d941:e7ff:cc75:9968/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:2dae:1ae3:c572:ed57/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:90ec:5051:54de:f345/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:5497:3bdc:6452:c67f/64 scope global temporary deprecated dynamic valid_lft 587sec preferred_lft 0sec inet6 [redacted-ipv6-/64]:[slaac-redacted]/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 587sec preferred_lft 587sec inet6 fe80::[ll-redacted]/64 scope link valid_lft forever preferred_lft forever root@pentos:~# systemctl start systemd-networkd root@pentos:~# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens5: mtu 1500 qdisc fq_codel state UP group default qlen 1000
[Touch-packages] [Bug 1839231] [NEW] updating bionic to 237-3ubuntu10.25 restarts systemd-networkd
Public bug reported: I updated my Ubuntu 18.04.2 server from systemd 237-3ubuntu10.24 to 237-3ubuntu10.25. This caused a restart of systemd-networkd, breaking all TCP-over-IPv6 connections. apt history entry: Start-Date: 2019-08-06 19:46:21 Commandline: apt-get dist-upgrade -y Requested-By: shivaram (1000) Upgrade: libsystemd0:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), udev:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libudev1:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd-sysv:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libpam-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libnss-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), base-files:amd64 (10.1ubuntu2.5, 10.1ubuntu2.6) End-Date: 2019-08-06 19:54:17 systemd journal output: Aug 06 19:47:40 pentos systemd[1]: Reloading. Aug 06 19:47:57 pentos systemd[1]: Reexecuting. Aug 06 19:47:58 pentos systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hie Aug 06 19:47:58 pentos systemd[1]: Detected architecture x86-64. Aug 06 19:47:58 pentos systemd[1]: Stopping Network Service... Aug 06 19:47:58 pentos systemd[1]: Stopped Network Service. Aug 06 19:47:58 pentos systemd[1]: Starting Network Service... Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Gained IPv6LL Aug 06 19:47:59 pentos systemd-networkd[11513]: Enumeration completed Aug 06 19:47:59 pentos systemd[1]: Started Network Service. Aug 06 19:47:59 pentos systemd-networkd[11513]: lo: Link is not managed by us Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: DHCPv4 address 192.168.1.103/24 via 192.168.1.1 Aug 06 19:47:59 pentos dbus-daemon[947]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2341' (uid=100 pid=11513 comm="/lib/systemd/systemd-network Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Configured ** Affects: systemd (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/1839231 Title: updating bionic to 237-3ubuntu10.25 restarts systemd-networkd Status in systemd package in Ubuntu: New Bug description: I updated my Ubuntu 18.04.2 server from systemd 237-3ubuntu10.24 to 237-3ubuntu10.25. This caused a restart of systemd-networkd, breaking all TCP-over-IPv6 connections. apt history entry: Start-Date: 2019-08-06 19:46:21 Commandline: apt-get dist-upgrade -y Requested-By: shivaram (1000) Upgrade: libsystemd0:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), udev:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libudev1:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd-sysv:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libpam-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libnss-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), base-files:amd64 (10.1ubuntu2.5, 10.1ubuntu2.6) End-Date: 2019-08-06 19:54:17 systemd journal output: Aug 06 19:47:40 pentos systemd[1]: Reloading. Aug 06 19:47:57 pentos systemd[1]: Reexecuting. Aug 06 19:47:58 pentos systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hie Aug 06 19:47:58 pentos systemd[1]: Detected architecture x86-64. Aug 06 19:47:58 pentos systemd[1]: Stopping Network Service... Aug 06 19:47:58 pentos systemd[1]: Stopped Network Service. Aug 06 19:47:58 pentos systemd[1]: Starting Network Service... Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Gained IPv6LL Aug 06 19:47:59 pentos systemd-networkd[11513]: Enumeration completed Aug 06 19:47:59 pentos systemd[1]: Started Network Service. Aug 06 19:47:59 pentos systemd-networkd[11513]: lo: Link is not managed by us Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: DHCPv4 address 192.168.1.103/24 via 192.168.1.1 Aug 06 19:47:59 pentos dbus-daemon[947]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2341' (uid=100 pid=11513 comm="/lib/systemd/systemd-network Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839231/+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
[Touch-packages] [Bug 1770919] Re: use_tempaddr is reset to 0, despite /etc/sysctl.d
systemd-networkd resets the value as per `systemd.network(5)`: 'IPv6PrivacyExtensions= [...] When "kernel", the kernel's default setting will be left in place. Defaults to "no".' This will be fixed with https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1750392 -- 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/1770919 Title: use_tempaddr is reset to 0, despite /etc/sysctl.d Status in systemd package in Ubuntu: New Bug description: I'm on a fresh install of 18.04 Server. It ships with the following file in /etc/sysctl.d: # cat /etc/sysctl.d/10-ipv6-privacy.conf # IPv6 Privacy Extensions (RFC 4941) # --- # IPv6 typically uses a device's MAC address when choosing an IPv6 address # to use in autoconfiguration. Privacy extensions allow using a randomly # generated IPv6 address, which increases privacy. # # Acceptable values: #0 - don’t use privacy extensions. #1 - generate privacy addresses #2 - prefer privacy addresses and use them over the normal addresses. net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 however, on boot, my physical NIC enp0s31f6 ends up with use_tempaddr set to 0: # for i in $(ls /proc/sys/net/ipv6/conf/*/use_tempaddr); do echo $i; cat $i; done; /proc/sys/net/ipv6/conf/all/use_tempaddr 2 /proc/sys/net/ipv6/conf/default/use_tempaddr 2 /proc/sys/net/ipv6/conf/enp0s31f6/use_tempaddr 0 /proc/sys/net/ipv6/conf/lo/use_tempaddr -1 Explicitly adding the following line to 10-ipv6-privacy.conf does not fix: net.ipv6.conf.enp0s31f6.use_tempaddr = 2 It appears that a later stage of the boot process reapplies the 0 value. A workaround is to add the line, then create an additional systemd unit that runs `systemctl restart systemd-sysctl.service` at the end of the boot process. I think the expected behavior, given the contents of /etc/sysctl.d/10-ipv6-privacy.conf, is that all NICs should come up with use_tempaddr set to 2. This does not happen; moreover, the workaround is counterintuitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770919/+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
[Touch-packages] [Bug 1770919] Re: use_tempaddr is reset to 0, despite /etc/sysctl.d
fixed affected package ** Package changed: systemtap (Ubuntu) => systemd (Ubuntu) -- 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/1770919 Title: use_tempaddr is reset to 0, despite /etc/sysctl.d Status in systemd package in Ubuntu: New Bug description: I'm on a fresh install of 18.04 Server. It ships with the following file in /etc/sysctl.d: # cat /etc/sysctl.d/10-ipv6-privacy.conf # IPv6 Privacy Extensions (RFC 4941) # --- # IPv6 typically uses a device's MAC address when choosing an IPv6 address # to use in autoconfiguration. Privacy extensions allow using a randomly # generated IPv6 address, which increases privacy. # # Acceptable values: #0 - don’t use privacy extensions. #1 - generate privacy addresses #2 - prefer privacy addresses and use them over the normal addresses. net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 however, on boot, my physical NIC enp0s31f6 ends up with use_tempaddr set to 0: # for i in $(ls /proc/sys/net/ipv6/conf/*/use_tempaddr); do echo $i; cat $i; done; /proc/sys/net/ipv6/conf/all/use_tempaddr 2 /proc/sys/net/ipv6/conf/default/use_tempaddr 2 /proc/sys/net/ipv6/conf/enp0s31f6/use_tempaddr 0 /proc/sys/net/ipv6/conf/lo/use_tempaddr -1 Explicitly adding the following line to 10-ipv6-privacy.conf does not fix: net.ipv6.conf.enp0s31f6.use_tempaddr = 2 It appears that a later stage of the boot process reapplies the 0 value. A workaround is to add the line, then create an additional systemd unit that runs `systemctl restart systemd-sysctl.service` at the end of the boot process. I think the expected behavior, given the contents of /etc/sysctl.d/10-ipv6-privacy.conf, is that all NICs should come up with use_tempaddr set to 2. This does not happen; moreover, the workaround is counterintuitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770919/+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
