On 26 February 2012 17:00, Dan Johansson <[email protected]> wrote: > On Sunday 26 February 2012 13.43:13 Dan Johansson wrote: >> On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: >> > >> > You guys are almost certainly running into the same problem as the one >> > I mentioned in the thread I just started. >> > >> > Try `pkill dhcpcd` and associate again. >> > >> > Unfortunately I couldn't figure out why all of a sudden dhcpcd decides >> > to start on boot. >> >> Yes, that was it, killing the dhcpcd made it possible to bring the interface >> up and associate with the AP. >> As openrc was one of the packages upgraded yesterday (0.9.8.4 -> 0.9.9.1) I >> assume (guess) that is why dhcpcd gets started at boot. >> Now I just have to figure out a way to stop this from happening. > > The problems seems to be that dhcpcd was started automatically as soon as a > service needed "the network" - in my case dhcpcd was started due to > /etc/init.d/sshd. > At the moment I have solved it with putting "rc_dhcpcd_provide="!net"" in > /etc/rc.conf > which prevents dhcpcd to start when sshd is started and wicd can now do it's > magic.
Ah, I could really have done with this thread earlier, but gmail had decided that it was spam :-/ What is strange is that it seems to work for some networks, but not for others, and I can't figure out how to predict on which dhcpd with succeed and on which it will not. I have access to three APs here (each with different SSIDs), and I can only connect to one of them; the other two have the dhcp failure. Very strange.
