Bugzilla – Bug 966999
IPv6 Privacy Extensions don't work with NetworkManager
Last modified: 2019-07-11 11:04:47 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Build Identifier: IPv6 Privacy Extensions don't work with NetworkManager in Leap 42.1 Reproducible: Always I tested it on native machine, also in a virtual machine with Virtualbox
I doubt that this is a bug in KDE... Reassigning to GNOME, the maintainers of NetworkManager in openSUSE.
(In reply to Achim Wirtz from comment #0) > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 > Firefox/44.0 > Build Identifier: > > IPv6 Privacy Extensions don't work with NetworkManager in Leap 42.1 Where did you set it up? Using nm-connection-editor ?
I can confirm this problem. This was on a system installed from openSUSE-Edu-li-f-e.x86_64-42.1.1.iso and using NetworkManager (default for Li-f-e). Network connection uses ethernet. In the NetworkManager settings for the connection, I configured the privacy options for IPv6 to prefer the temporary address. However, I am seeing only the permanent IPv6 address. The file "/etc/NetworkManager/system-connections/Wired connection 1" contains (among other things): --- begin quote --- [ipv6] dns-search= ip6-privacy=2 method=auto --- end quote --- Note that the system has been rebooted several times since the configuration was set. On my main desktop, where I use "wicked", privacy options are working properly.
In reply to Wolfang Bauer: the bug also exists in KDE.
(In reply to Eberhard Harbrink from comment #4) > In reply to Wolfang Bauer: > the bug also exists in KDE. And what's your point? If it is a problem in NetworkManager, it will of course also exist in KDE if you are using NetworkManager in KDE.
(In reply to Wolfgang Bauer from comment #5) > (In reply to Eberhard Harbrink from comment #4) > > In reply to Wolfang Bauer: > > the bug also exists in KDE. > > And what's your point? > > If it is a problem in NetworkManager, it will of course also exist in KDE if > you are using NetworkManager in KDE. Ok, that was a misunderstanding from my side ;-) I interpreted your remark that way, that you won't experience the bug when you are using kde, and I only wanted to point out, that I get this problem too using kde. Which code is responsible for the bug, I don't know. I'm only a user ;-)
I can confirm this bug. Everything works fine if OpenSuse is configure to use wickedd. Can we expect a fix for Leaf 42.1 or should we wait the next version?
To cut a long story short: I am not convinced it's a bug in NetworkManager. Network manager has supported privacy extensions for about 2 years now. After some digging I found this: https://bugzilla.gnome.org/show_bug.cgi?id=705170#c5 The point is, in my case: ) NM fails to give network interface any temporary address 2) NM gives network interface an IPv6 address as /128 and not /64 3) NM prints a warning in logs that says "libnl does not support extended IFA_FLAGS ..." Basically it behaves exactly as described in the post I quoted. I'd start looking into libnl.
UPDATE I have update both libnl3 and libnl-config 3.2.25 (it's the official stable release for openSUSE 13.2) and now everything looks fine. Can we have 3.2.25 for leap 42.1 too?
Scott, Frederic, libnl3 in Leap 42.1 is a SLE12 package. Can we have this checked? As Lorenzo confirms, the fix is 'somewhere' between 3.2.23 (shipped in Leap 42.1) and 3.2.25 (tested by Lorenzo)
(In reply to Dominique Leuenberger from comment #10) > Scott, Frederic, libnl3 in Leap 42.1 is a SLE12 package. Can we have this > checked? As Lorenzo confirms, the fix is 'somewhere' between 3.2.23 (shipped > in Leap 42.1) and 3.2.25 (tested by Lorenzo) I'm a bit reluctant to update to libnl3 3.2.25 in SLE12, since it will require a lot of ressources on our side and it adds new API. Fedora has released 3.2.24 as an update in F20 to fix Privacy Extensions (rh#1047139) so maybe we could narrow our research around which exact commit we can extract to fix the issue.
It's this one: http://git.infradead.org/users/tgr/libnl.git/commit/dcc0baac020e033c4325e4d89c92aaab03f01b01
You'd probably need this too: http://git.infradead.org/users/tgr/libnl.git/commit/b203c89d862a6ae3e82122fe1b6882b427d53551
Hi all. I've also run into (detected for the first time) this bug today. Leap 42.1, KDE Plasma, Network Manager. As said before, works fine with wicked. With much help from #suse today maybe we can help a little bit: We found a temporary workaround: sudo sysctl -w net.ipv6.conf.<INTERFACE>.accept_ra_pinfo=1 will get the "global temporary dynamic" ipv6 address for the desired <INTERFACE>. After a while, be patient. And only until next reboot, not persistent. And we found a very detailed described bug in RedHat, same issue: https://bugzilla.redhat.com/show_bug.cgi?id=1279242 Maybe worth looking is the last entry from Peter Bieringer: "I've played around with a scriptlet and it turned out, that something near/inbetween DHCPv6 will reset accept_ra_pinfo even if tempaddr is enabled"
are there any activities on this bug? any plans when this issue is going to be fixed? any plans for Leap 42.1?
again after ~ one month without any answer: are there any activities on this bug? any plans when this issue is going to be fixed? any plans for Leap 42.1?
CC @Leap 42.2 RM - considering that we still have the same version libnl3 in 42.2, there is a high chance that this bug is still present there
Peter, since you assigned the bug to you, any update?
No respsonse. Jonathan, could you take a look please?
@Ludwig I will start on this in the next 24 hours. Been traveling and now home sick.
Assigning back to Peter, since he has started to work on it a few days ago. I'd be glad to help if there is anything I can help with.
ping!
I'll note that this is still an issue with 42.2. (Not sure if the version should be changed for the bug). I am changing the component from "Gnome" to "Network". I'm seeing it with KDE (Plasma 5). I don't think the desktop is relevant. However, this is specific to NetworkManager. I don't see the problem if I use "wicked".
This appears to still be an issue with 42.3. Accordingly, I have changed it to reference 42.3.
According to https://bugzilla.gnome.org/show_bug.cgi?id=705170#c9, the patches to properly support the privacy extensions were released in version 3.2.24
(In reply to Stelian Ionescu from comment #25) > According to https://bugzilla.gnome.org/show_bug.cgi?id=705170#c9, the > patches to properly support the privacy extensions were released in version > 3.2.24 Hi Stelian, not sure if I maybe misunderstand something, but your mentioned issue has it's last activity on 2014-01-30, and you mention "version 3.2.24". This bug here was opened long after that on 2016-02-17, and at least 42.2 still has this bug. Looking on my (still 42.2) box I've NetworkManager in 1.0.12.X, and https://wiki.gnome.org/Projects/NetworkManager/ lists NetworkManager STABLE as 1.8.0, from "10 May 2017". What is "version 3.2.24"? Gnome itself? If so, how would be the way into KDE? Thanks, Michael
I meant the bug is in libnl3, and the fixing patches were released in version 3.2.24, whereas openSUSE 42.3 is stuck with 3.2.23
Stelian, thank you very much for clarification!
(In reply to Stelian Ionescu from comment #27) > I meant the bug is in libnl3, and the fixing patches were released in > version 3.2.24, whereas openSUSE 42.3 is stuck with 3.2.23 - promised for libln3 > 3.2.24 - 15.0 has libln3 3.3.0 and I'm getting "global temporary dynamic" IPv6 addresses now with NetworkManager, Yabba Dabba Doo!!! Thanks to all who fixed this long-open bug!!! Not sure about the appropriate bugzilla handling of this issue, as it was opened for 42.3, not sure if "wontfix" or "resolved" or something else, so I'm letting this issue open.
This is automated batch bugzilla cleanup. The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please feel free to reopen this bug against that version (!you must update the "Version" component in the bug fields, do not just reopen please), or alternatively create a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime