I just realised that this bug also impacts NetworkManager, at least on
Vivid: I set the property "ipv6.ip6-privacy" on the default wired
Ethernet interface to 0 (in order to prevent a remote CIFS mount from
freezing every few hours), however after a reboot, privacy extensions
remained active. My assumption is that NetworkManager configured the
interface correctly (without privacy extensions) early on during the
boot process, only to have the procps' 10-ipv6-privacy.conf overwrite it
moments later. Disabling 10-ipv6-privacy.conf solved this issue too.
** Summary changed:
- 10-ipv6-privacy.conf stomps on user-configured "privext" option
+ 10-ipv6-privacy.conf stomps on the ifup/NetworkManager
"privext"/"ipv6.ip6-privacy" settings
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- 10-ipv6-privacy.conf stomps on the ifup/NetworkManager
"privext"/"ipv6.ip6-privacy" settings
+ procps' 10-ipv6-privacy.conf stomps on the ifup/NetworkManager
"privext"/"ipv6.ip6-privacy" settings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497166
Title:
procps' 10-ipv6-privacy.conf stomps on the ifup/NetworkManager
"privext"/"ipv6.ip6-privacy" settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1497166/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
