>> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks >> are not known > >Looking at the upstream commit description, isn't it just that a DHCPv6 lease >expires and the >server NAKs a request for the same IP again? Or is that not >sufficient to trigger the problem. > Yes, when having a look at the previously collected logs, that seems to be the case (journalctl -u NetworkManager.service).
Some of our computers get this problem more often that other. Some persons claim that they have never seen the problem. That is the part that is unclear. >In any case, I appreciate there might be difficulty in testing the fix, but >what's the actual >criteria you propose to use to decide when the bug is to be >marked verification-done-bionic? In the best of worlds I would like to simulated environment where dhcp- packages could be controlled, but that is not feasible. I have been running this patch on two computers since 2022-04-13 and haven't seen the problem since. One laptop (restarted every day) and one desktop that is always on. The desktop has been running for 29 days continuously according to syslog, without me having to manually remove dhcp lease files and restart network manager. Ideas for getting confidence of this change: We could ask more users who have experienced this error to install this change and confirm if they experience lost ipv6 addresses after installing patched version. Another idea is to shutdown computer in single user mode (without network), edit the dhcp6 lease file in a way so that dhcp-server will respond with NACK when booting up in multi-user mode. What to change in the lease file I do not know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969901 Title: network-manager fails to renew ipv6 address Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Incomplete Bug description: [Impact] * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is used. * Network manager might kill dhclient(6) and fail to start it again causing the IPv6 address to be lost on a network that uses mixed IPv4/IPV6. The network status will still be seen as online in gnome since ipv4 is still active. The user then have to manually remove the dhcpv6 lease files and restart ipv6 connection/restart network manager to regain IPv6 connectivity. * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version is based on 1.10.6): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f * Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=783391 [Test Plan] * The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known but includes using both IPv4 and IPv6, both using dhcp. [Where problems could occur] * The change is in the dchp lease expiration handling so verify that there is no regression in dhcp renewals on different type of configuration include IPv6 [Other Info] * We have tested this patch on a couple of clients where we have seen this this problem. If this patch is feasible to include in Ubuntu 18.04 we could request more users to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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
