This bug was fixed in the package systemd - 237-3ubuntu10.39
---------------
systemd (237-3ubuntu10.39) bionic; urgency=medium
[ Dariusz Gadomski ]
*
d/p/lp1762391/0001-Call-getgroups-to-know-size-of-supplementary-groups-.patch,
d/p/lp1762391/0002-user-util-tweak-to-in_gid.patch,
d/p/lp1762391/0003-user-util-Add-helper-functions-for-gid-lists-operati.patch,
d/p/lp1762391/0004-execute-Restore-call-to-pam_setcred.patch,
d/p/lp1762391/0005-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch,
d/p/lp1762391/0006-test-Add-tests-for-gid-list-ops.patch,
d/p/lp1762391/0007-execute-add-const-to-array-parameters-where-possible.patch,
d/p/lp1762391/0008-execute-allow-pam_setcred-to-fail-ignore-errors.patch:
- Restore call to pam_setcred (LP: #1762391)
[ Ioanna Alifieraki ]
* d/p/lp1860548/0001-Revert-Replace-use-of-snprintf-with-xsprintf.patch,
d/p/lp1860548/0002-job-truncate-unit-description.patch:
- use snprintf instead of xsprintf (LP: #1860548)
[ Dan Streetman ]
* d/p/lp1833193-network-update-address-when-static-address-was-alrea.patch:
- Update lft when static addr was cfg by dhcp (LP: #1833193)
*
d/p/lp1849261/0001-core-when-we-can-t-enqueue-OnFailure-job-show-full-e.patch,
d/p/lp1849261/0002-core-don-t-trigger-OnFailure-deps-when-a-unit-is-goi.patch:
- Only trigger OnFailure= if Restart= is not in effect (LP: #1849261)
* d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
- set ipv6 mtu at correct time (LP: #1671951)
* d/p/lp1845909/0001-networkd-honour-LinkLocalAddressing.patch,
d/p/lp1845909/0002-networkd-fix-link_up-12505.patch,
d/p/lp1845909/0003-network-do-not-send-ipv6-token-to-kernel.patch,
d/p/lp1845909/0004-network-rename-linux_configure_after_setting_mtu-to-linux.patch,
d/p/lp1845909/0005-network-add-link-setting_genmode-flag.patch,
d/p/lp1845909/0006-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch,
d/p/lp1845909/0007-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch,
d/p/lp1845909/0008-network-drop-IPv6LL-address-when-LinkLocalAddressing.patch:
- if LinkLocalAddressing=no prevent creation of ipv6ll (LP: #1845909)
* d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch:
- enable ipv6 when needed (LP: #1859862)
* d/p/lp1836695-networkd-Add-back-static-routes-after-DHCPv4-lease-e.patch:
- (re)add static routes after getting dhcp4 addr (LP: #1836695)
* d/t/storage:
- fix buggy test (LP: #1831459)
- without scsi_debug, skip test (LP: #1847816)
-- Dan Streetman <ddstr...@canonical.com> Thu, 06 Feb 2020 10:00:49
-0500
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1859862
Title:
networkd doesn't re-enable ipv6 unless mtu is set
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
In Progress
Bug description:
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is
configured with ipv6 networking, networkd will not enable ipv6 via the
procfs setting unless the interface mtu is also set to a custom value,
that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee
/proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are
configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6;
modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
(be sure to set the MTU config to something other than its current
mtu)
verify ipv6 is still disabled and has no addresses, then restart and
check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the
regression potential could cause failure to properly set/create ipv6
addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765
which is included starting in v243, so it is included already in
Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit
44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting
in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic,
this is a regression introduced by bug 1850704. However, manual
disabling of ipv6 is very unusual, so this bug is unlikely to have an
impact to many systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1859862/+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
