On Tue, 2011-10-11 at 15:03 -0500, Patrick McMunn wrote: > As far as I know, dhcpcd has always been capable of working as a > daemon. I guess NM just doesn't like it that way. I had it starting up > at boot and daemonizing per tutorials I had followed, but then again > the tutorials I had followed were aimed at using Gentoo's networking > structure - not tools like NM. > > So I disabled dhcpcd from starting at boot. Now everything works > perfectly. I even have WPA encryption working over ad-hoc, and until > recently I had been led to believe that was impossible.
Hmm, this is something I guess we need to look into, since NM would need some adjustment to support this. I guess we'd also need to know if dhcpcd was in this configuration or not, since that affects how NM handles the process exiting. > The only loose end is with ifnet. I had to disable it to get NM to > behave itself properly, so I'll report those issues to ifnet's > upstream. Yeah, the Gentoo people are pretty good about these sorts of things. It might come back to this list eventually though :) Dan > Thank you very much for your help, Dan. > > >> Huh. Looks like dhcpcd has changed and now sends commands to a daemon? > >> That's fine, but the code doesn't expect that; it expects that the DHCP > >> process it starts will continue until NM tells it to quit. Also looks > >> like in this configuration there's no way to get the DHCP options back > >> to NM, actually. So the main problem is that dhcpcd is acting in a way > >> that NM doesn't expect here, which hasn't been the case with dhcpcd > >> before. > >> > >> Dan > _______________________________________________ > networkmanager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ networkmanager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
