Am Mon, 18. Jun 2012 um 19:12:42 +0300 schrieb Edward J. Shornock: > * Craig Small <[email protected]> [08-06-2012 03:38 EEST]: >> Can you check that all three items are not set? I suspect it is to do >> with the configuration being setup before the interface is configured. > > For some reason I can reproduce this on two live systems (Sid and > Wheezy) but it works perfectly in a Wheezy virtual machine. > > The settings after boot-up: > > # awk -F'=' '{print $1}' /etc/sysctl.d/*.conf |while read foo; do sysctl > $foo;done > net.ipv6.conf.all.use_tempaddr = 2 > net.ipv6.conf.default.use_tempaddr = 2 > net.ipv6.conf.eth0.use_tempaddr = 0 > > I've not figured out what's stopping it from working on these two boxes > (one is an older system and the other is much "beefier").
To take effect, those changes need to be setup before the interface is brought up. You will see it work if you down/up eth0 after boot. With dependency based boot and no dependency between procps and networking service, they tend to get the same priority on my system. But networking is executed before procps, so I have the same problem as you. (Which I circumvented by adding networking as Required-Start in the procps init script.) But I would appreciate a solution provided out of the box because a user should expect the settings to take effect - not only by chance. I think this will hit a lot of people who don't know about this and just enable privacy extensions and think everything is ok. Dirk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
