[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2012-01-19 Thread Mathieu Trudel-Lapierre
Of course, don't hesitate to set this bug back to New if you feel I've missed or forgotten something :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803739 Title: value set in /etc/sysctl.conf not

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2012-01-19 Thread Mathieu Trudel-Lapierre
I think what you're really running into is that wlan0 comes up after the sysctls are applied. Using net.ipv6.conf.all.use_tempaddr should fix this in Precise now for devices that existed prior to the sysctls being applied, and net.ipv6.conf.default.use_tempaddr was already meant to take care of

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-12-12 Thread Mathieu Trudel-Lapierre
** Changed in: procps (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803739 Title: value set in /etc/sysctl.conf not used at boot time To manage notifications

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-12-05 Thread Mathieu Trudel-Lapierre
I can somewhat reproduce this on my system, except the device that comes up early is (more expectedly than wlan0) eth0. All interfaces but that one do get the right value set for use_tempaddr; and there seems to be something fishy going on when setting these values in sysctl anyway:

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-07-03 Thread Dave Gilbert
Hi Yves, OK that means most stuff is working as it should; I think stop/waiting for procps is normal - it just does its setup stuff and stops again. Two thoughts then; I wonder whether at the time procps runs during startup wlan0 has been found yet? If it's not then I guess

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-07-03 Thread Yves Dorfsman
Yes I thought about wlan0 not being available, and I purposely rebooted the laptop making sure that the network kill switch was on etc... wlan0 came up right away, but net.ipv6.conf.wlan0.use_tempaddr was equal zero (the other ones were equal to one). I also check the spelling and copied and

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-07-02 Thread Dave Gilbert
Hi Yves, A few things to try: 1) If you do start procps do the values get set? (Are there any errors?) 2) what about writing directly to the entry - i.e. (from a root shell - not a sudo at the start of the line!) echo 2 /proc/sys/net/ipv6/conf/all/use_tempaddr **

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-07-02 Thread Yves Dorfsman
2) what about writing directly to the entry Yes, that works, even just doing sysctl net.ipv6.conf.wlan0.use_tempaddr=2 works. 1) If you do start procps do the values get set? Huh... it does. This is confusing. Right after boot, three of the four values are set (all, eth0 and eth1). Wlan0

[Bug 803739] Re: value set in /etc/sysctl.conf not used at boot time

2011-06-29 Thread Yves Dorfsman
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803739 Title: value set in /etc/sysctl.conf not used at boot time To manage notifications about this bug go to: