** Description changed:

- 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.
+ [Impact]
  
- This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
- This was fixed in 1.12.0.
+  * 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.
  
- Could you consider including the below patch on ubuntu 18.04?
+  * 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
  
- 
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
+  * Upstream bug:
+    https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
- 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.
+ [Test Plan]
  
- cat
- 
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
- |sed
- 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
- > modified_patch.patch
+  * 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.
  
- 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)
+ [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.

** Patch 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

** Description changed:

  [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 affects Ubuntu 18.04 where Network Manager version 1.10.6 is
+ used.
  
-  * 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
+  * 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.
  
-  * Upstream bug:
-    https://bugzilla.gnome.org/show_bug.cgi?id=783391
+  * 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.
+  * 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.
+  * 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.
+  * 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.

-- 
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:
  New

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]

   * 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.

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

Reply via email to