1 |
I just switched my home LAN from wired to all wifi and I'm having trouble |
2 |
with NetworkManager at boot time. |
3 |
|
4 |
I have systemd start NetworkManager at boot because I need the internet |
5 |
for ntpdate and to start the nfs server for the LAN. Before I switched |
6 |
to all-wireless this method worked perfectly, but no longer. |
7 |
|
8 |
After bootup I see that NetworkManager started wpa_supplicant in the |
9 |
background, but apparently does *not* run dhcpcd. (The wlan0 is up |
10 |
but it has no IP address and the routing table is empty.) |
11 |
|
12 |
As an alternative to NetworkManager I can have systemd start dhcpcd |
13 |
at boot, which almost (but not quite) works well enough. This |
14 |
causes a race condition because wlan0 takes several seconds to come |
15 |
up properly and by then both ntpdate and nfs-server have already |
16 |
run and failed. |
17 |
|
18 |
So, I asked myself, why not have systemd start dhcpcd at boot in |
19 |
addition to NetworkManager? |
20 |
|
21 |
The reason that fails is that they both start wpa_supplicant in |
22 |
the background and the two instances interfere with each other. |
23 |
|
24 |
Anyone see a way around this catch22? |
25 |
|
26 |
|
27 |
Thanks. |