1 |
On Mon, Oct 13, 2014 at 7:39 PM, walt <w41ter@×××××.com> wrote: |
2 |
> |
3 |
> I just switched my home LAN from wired to all wifi and I'm having trouble |
4 |
> with NetworkManager at boot time. |
5 |
> |
6 |
> I have systemd start NetworkManager at boot because I need the internet |
7 |
> for ntpdate and to start the nfs server for the LAN. Before I switched |
8 |
> to all-wireless this method worked perfectly, but no longer. |
9 |
> |
10 |
> After bootup I see that NetworkManager started wpa_supplicant in the |
11 |
> background, but apparently does *not* run dhcpcd. (The wlan0 is up |
12 |
> but it has no IP address and the routing table is empty.) |
13 |
> |
14 |
> As an alternative to NetworkManager I can have systemd start dhcpcd |
15 |
> at boot, which almost (but not quite) works well enough. This |
16 |
> causes a race condition because wlan0 takes several seconds to come |
17 |
> up properly and by then both ntpdate and nfs-server have already |
18 |
> run and failed. |
19 |
> |
20 |
> So, I asked myself, why not have systemd start dhcpcd at boot in |
21 |
> addition to NetworkManager? |
22 |
> |
23 |
> The reason that fails is that they both start wpa_supplicant in |
24 |
> the background and the two instances interfere with each other. |
25 |
> |
26 |
> Anyone see a way around this catch22? |
27 |
|
28 |
Do you have "All users may connect" unticked in the NM applet or |
29 |
"permissions=user:walt:;" in the NM connection's config? |