* [gentoo-user] [systemd] Is this a NetworkManager bug?
@ 2014-10-13 23:39 99% walt
0 siblings, 0 replies; 1+ results
From: walt @ 2014-10-13 23:39 UTC (permalink / raw
To: gentoo-user
I just switched my home LAN from wired to all wifi and I'm having trouble
with NetworkManager at boot time.
I have systemd start NetworkManager at boot because I need the internet
for ntpdate and to start the nfs server for the LAN. Before I switched
to all-wireless this method worked perfectly, but no longer.
After bootup I see that NetworkManager started wpa_supplicant in the
background, but apparently does *not* run dhcpcd. (The wlan0 is up
but it has no IP address and the routing table is empty.)
As an alternative to NetworkManager I can have systemd start dhcpcd
at boot, which almost (but not quite) works well enough. This
causes a race condition because wlan0 takes several seconds to come
up properly and by then both ntpdate and nfs-server have already
run and failed.
So, I asked myself, why not have systemd start dhcpcd at boot in
addition to NetworkManager?
The reason that fails is that they both start wpa_supplicant in
the background and the two instances interfere with each other.
Anyone see a way around this catch22?
Thanks.
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-10-13 23:39 99% [gentoo-user] [systemd] Is this a NetworkManager bug? walt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox