| 2022-04-22 08:22:39 |
Håkan Kvist |
bug |
|
|
added bug |
| 2022-04-22 08:23:26 |
Håkan Kvist |
description |
We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 18.04.
Unfortunately next LTS release is not yet an option.
This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
Could you consider including the below patch on ubuntu 18.04?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
The patch can be applied with some adjustements on top of the version of network manager included in Bionic (pull-lp-source network-manager bionic). A function name has changed, changing the function name in the downloaded patch is enough to apply the patch.
cat ../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch |sed 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g' > modified_patch.patch
This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi) |
We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 18.04.
Unfortunately next LTS release is not yet an option for us.
This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
Could you consider including the below patch on ubuntu 18.04?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
The patch can be applied with some adjustements on top of the version of network manager included in Bionic (pull-lp-source network-manager bionic). A function name has changed, changing the function name in the downloaded patch is enough to apply the patch.
cat ../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch |sed 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g' > modified_patch.patch
This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi) |
|
| 2022-04-22 08:36:55 |
Håkan Kvist |
description |
We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 18.04.
Unfortunately next LTS release is not yet an option for us.
This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
Could you consider including the below patch on ubuntu 18.04?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
The patch can be applied with some adjustements on top of the version of network manager included in Bionic (pull-lp-source network-manager bionic). A function name has changed, changing the function name in the downloaded patch is enough to apply the patch.
cat ../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch |sed 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g' > modified_patch.patch
This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi) |
We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 18.04.
Unfortunately next LTS release is not yet an option for us.
This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
This was fixed in 1.12.0.
Could you consider including the below patch on ubuntu 18.04?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
The patch can be applied with some adjustements on top of the version of network manager included in Bionic (pull-lp-source network-manager bionic). A function name has changed, changing the function name in the downloaded patch is enough to apply the patch.
cat ../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch |sed 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g' > modified_patch.patch
This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi) |
|
| 2022-04-27 06:12:39 |
Håkan Kvist |
description |
We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 18.04.
Unfortunately next LTS release is not yet an option for us.
This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
This was fixed in 1.12.0.
Could you consider including the below patch on ubuntu 18.04?
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
The patch can be applied with some adjustements on top of the version of network manager included in Bionic (pull-lp-source network-manager bionic). A function name has changed, changing the function name in the downloaded patch is enough to apply the patch.
cat ../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch |sed 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g' > modified_patch.patch
This has been tested on some devices and so far we have not seen any problems
ipv4 only network (cable/wifi)
ipv6/ipv4 mixed network (cable/wifi) |
[Impact]
* 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]
* This patch could possibly break networking using and that would be bad.
Network manager should be able to restart connection more properly with
this patch though.
[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. |
|
| 2022-04-27 06:14:07 |
Håkan Kvist |
attachment added |
|
Debdiff against network-manager_1.10.6-2ubuntu1.5 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5584241/+files/network-manager_1.10.6-2ubuntu1.6.debdiff |
|
| 2022-04-27 06:15:25 |
Håkan Kvist |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2022-04-27 06:17:38 |
Håkan Kvist |
description |
[Impact]
* 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]
* This patch could possibly break networking using and that would be bad.
Network manager should be able to restart connection more properly with
this patch though.
[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. |
[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]
* This patch could possibly break networking using and that would be bad.
Network manager should be able to restart connection more properly with
this patch though.
[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. |
|
| 2022-05-14 20:30:24 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Confirmed |
|
| 2022-05-31 11:46:30 |
Sebastien Bacher |
network-manager (Ubuntu): importance |
Undecided |
Low |
|
| 2022-05-31 11:46:30 |
Sebastien Bacher |
network-manager (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2022-05-31 11:49:31 |
Sebastien Bacher |
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]
* This patch could possibly break networking using and that would be bad.
Network manager should be able to restart connection more properly with
this patch though.
[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. |
[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. |
|
| 2022-06-01 13:21:14 |
Robie Basak |
nominated for series |
|
Ubuntu Bionic |
|
| 2022-06-01 13:21:14 |
Robie Basak |
bug task added |
|
network-manager (Ubuntu Bionic) |
|
| 2022-06-01 13:21:21 |
Robie Basak |
network-manager (Ubuntu Bionic): status |
New |
Incomplete |
|
| 2022-06-20 16:59:09 |
Mathew Hodson |
network-manager (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2022-06-23 13:54:18 |
Håkan Kvist |
attachment added |
|
dhcp_v4_a.conf https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5599243/+files/dhcp_v4_a.conf |
|
| 2022-06-23 13:55:46 |
Håkan Kvist |
attachment removed |
dhcp_v4_a.conf https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5599243/+files/dhcp_v4_a.conf |
|
|
| 2022-06-23 13:57:11 |
Håkan Kvist |
attachment added |
|
dhcpd configuration files for testing https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5599244/+files/dhcpd_configuration_files.zip |
|
| 2022-08-30 18:03:10 |
Håkan Kvist |
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. |
[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 test requires three computers
* one computer runing isc dhcpd server (with network configured static)
* one computer running patched network manager
* one computer running vanilla ubuntu
The idea is to execute on an isolated network and trigger the error by changing
ip range handed out by the dhcp-server to force a nack response back to the
clients.
Expected result
* patched network keeps dhclient6 alive
* vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted
ON THE SERVER
# Disable app-armor, as it has rules restricting dhcpd
aa-teardown
# install isc dhcpserver
isc-dhcp-server
# configure network static
sudo nmcli connection modify "${CONNECTION_NAME}" \
ipv4.method "manual" \
ipv4.addresses "192.168.1.1/24" \
ipv4.gateway "192.168.1.254" \
ipv4.dns "192.168.1.1" \
ipv6.method "manual" \
ipv6.addresses "2001:db8:0:1::1/64" \
ipv6.gateway "2001:db8:0:1::ffbb" \
ipv6.dns "2001:db8:0:1::1/64"
mkdir -p tmp
touch tmp/dhcpd4_a.leases
touch tmp/dhcpd4_b.leases
touch tmp/dhcpd6_a.leases
touch tmp/dhcpd6_b.leases
Then it is time to execute dhcpd
-f - run in foreground
-d - print errors to stderr instead of syslog
# Start in separate terminals
dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
Press ctrl-C to kill servers, then restart with the b configurations
dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
Then leases to expire (check for clients that kills dhclient)
Press ctrl-C to kill servers, then restart with the a configurations
ON THE CLIENTS
Setup:
Configure ipv6 network in settings to use dhcp (using the gui)
Test:
check that dhcp clients are still running:
ps aux|grep dhclient
Expected in output
one client for dhcpv4
one client for dhcpv6
Also check network manager status :
journalctl -u NetworkManager.service
journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
if dhclient is not running:
stop network in gui
remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the lease for the client not running.
start network in gui
if dhclients are running:
wait additional ten minutes, repeat from beginning of test
[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. |
|
| 2022-09-21 13:40:47 |
Jeremy Bícha |
network-manager (Ubuntu Bionic): status |
Incomplete |
In Progress |
|
| 2022-09-21 14:23:23 |
Robie Basak |
network-manager (Ubuntu Bionic): status |
In Progress |
Incomplete |
|
| 2022-09-21 14:23:58 |
Jeremy Bícha |
bug |
|
|
added subscriber Jeremy Bicha |
| 2022-10-07 14:29:21 |
Håkan Kvist |
attachment added |
|
updated patch including d017022dfc7e531c23caddeac7b3a8b03b1aa5d0 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5622069/+files/network-manager_1.10.6-2ubuntu1.6-update.debdiff |
|
| 2023-05-12 16:12:19 |
Mathew Hodson |
tags |
|
patch |
|
| 2023-05-12 16:12:40 |
Mathew Hodson |
network-manager (Ubuntu Bionic): status |
Incomplete |
Triaged |
|
| 2023-06-05 10:30:04 |
Julian Andres Klode |
network-manager (Ubuntu Bionic): status |
Triaged |
Won't Fix |
|
| 2023-06-05 10:30:05 |
Julian Andres Klode |
removed subscriber Ubuntu Sponsors |
|
|
|
