SRUing the newer version failed since it changed behaviour in some
configuration which created issue for existing users.
There isn't anyone currently working on resolving those issues so it's
more realistic to untarget from Bionic.
If the problem really needs to be resolved in that serie best to
** Changed in: network-manager (Ubuntu Cosmic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
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/1796622
The bionic fix is included in the upstream 1.10.14 release:
https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu1
1.12.6 has the fix for cosmic.
** Changed in: network-manager (Ubuntu Cosmic)
Importance: Undecided => High
--
You received this bug notification because you are
This is fixed in Disco; I opened Bionic and Cosmic tasks since the bug
needs to be open in some way for it to be tracked.
** Changed in: network-manager (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Also affects: network-manager (Ubuntu Cosmic)
Importance: Undecided
The issue was fixed in 1.12.6 which has been uploaded to disco,
https://launchpad.net/ubuntu/+source/network-manager/1.12.6-0ubuntu1
** Changed in: network-manager (Ubuntu Disco)
Status: New => Fix Committed
** Changed in: network-manager (Ubuntu Disco)
Assignee: Andrea Azzarone
** Changed in: network-manager (Ubuntu Disco)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Disco)
Assignee: (unassigned) => Andrea Azzarone (azzar1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It should be yes, but I'd like to look at the changes needed before
going any further. Looking at the diff, it doesnt look too bad for the
current version on n-m. With some luck it will be backported by
upstream, if not we'll take a look.
Release of Cosmic is next week, so I dont think this
Thank you Will!
We are running Ubuntu 16.04 with network-manager version 1.2.6, that will be
fixed too?
--
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/1796622
Investigation found that DAD timeout for IPv6 seems to be not
implemented for network manager [1]. And only support up to IPv4. It
looks like a limitation but couldn't find any writing confirmation for
this limitation.
[1] https://developer.gnome.org/NetworkManager/stable/settings-ipv6.html
--
Upstream fix: https://github.com/NetworkManager/NetworkManager/pull/228
This will be ported to all supported releases soon, so we should be able
to pick that up easily enough.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Upstream issue reported:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/57
Thanks for looking into it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Spoke to upstream. They will look in to this and get it fixed. I've
asked David to log it upstream and we can link to that here.
We should look at backport the fixes and SRUing to Bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hi Bryan,
Here is the information for those 2 cases:
v6LC_3_2_4_C - Prefix Lifetime less than the Remaining Lifetime and the
Remaining Lifetime is less than 2 hours
http://fnet.sourceforge.net/ip6_tests/Self_Test_5-0-0/addr.p2/v6LC_3_2_4_C.html
RA_gt2lt2 - Prefix Lifetime less than 2 hours and
** Information type changed from Private Security to Public Security
--
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/1796622
Title:
NetworkManager IPv6 DAD
14 matches
Mail list logo
