This patch changes the way how existing installations get their IPv6 address which is something that really shouldn't be done in an update to an LTS release in my opinion. Even worse it completely overrules configuration in /etc/sysctl.d/10-ipv6-privacy.conf and if you change the configuration on a running system network-manager changes it back within a second! For example
runge:~# sysctl -w net.ipv6.conf.eth0.use_tempaddr=0 net.ipv6.conf.eth0.use_tempaddr = 0 wait a few seconds while network-manager says something about disconnected wired interface runge:~# sysctl net.ipv6.conf.eth0.use_tempaddr net.ipv6.conf.eth0.use_tempaddr = 2 Network-manager shouldn't overrule the system configuration, especially when network-manager currently has no toggle for privacy extensions. If you think changing the default is okay in a stable update (I really don't), at least it should be done in a way that makes it possible to easily go back to the previous behaviour. Given that the sysctl default is already what we want as default, I don't see why NM has to explicitly set it again and if it doesn't do that it would be possible to change the configuration in /etc/sysctl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990011 Title: use_tempaddr is *still* not set properly for default eth0 connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/990011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
