On Fri, 2014-09-12 at 22:49 +0300, Lampropoulos Anastasios wrote: > Hi, > > ● NetworkManager.service - Network Manager > Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) > Active: active (running) since Thu 2014-09-11 18:27:21 EEST; 1 day > 4h ago > Main PID: 1312 (NetworkManager) > CGroup: /system.slice/NetworkManager.service > └─1312 /usr/bin/NetworkManager --no-daemon > > Sep 11 18:27:23 archonacer NetworkManager[1312]: <info> Activation > (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) complete. > Sep 11 18:27:23 archonacer NetworkManager[1312]: dhcpcd[1319]: sending > commands to master dhcpcd process
Ok, this is the issue. NM expects to receive a response from dhcpcd, but the dhcpcd that NM spawns is just talking to a master instance which does not communicate back to NM at all. If you disable the main system dhcpcd service, I'm betting that will solve the problem. It won't prevent NetworkManager from using dhcpcd at all, because NM spawns a private instance. systemd mask dhcpcd Dan > Sep 12 18:56:28 archonacer NetworkManager[1312]: <warn> Connection > disconnected (reason -3) > Sep 12 18:56:28 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: completed -> disconnected > Sep 12 18:56:28 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: disconnected -> scanning > Sep 12 18:56:29 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: scanning -> authenticating > Sep 12 18:56:29 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: authenticating -> associating > Sep 12 18:56:29 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: associating -> associated > Sep 12 18:56:29 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: associated -> 4-way handshake > Sep 12 18:56:29 archonacer NetworkManager[1312]: <info> (wlp3s0): > supplicant interface state: 4-way handshake -> completed > ● dhcpcd.service - dhcpcd on all interfaces > Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled) > Active: active (running) since Thu 2014-09-11 20:58:39 EEST; 1 day > 1h ago > Process: 202 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, > status=0/SUCCESS) > Main PID: 206 (dhcpcd) > CGroup: /system.slice/dhcpcd.service > └─206 /usr/bin/dhcpcd -q -b > > Sep 12 18:56:28 archonacer dhcpcd[206]: wlp3s0: deleting default route > via 192.168.1.1 > Sep 12 18:56:29 archonacer dhcpcd[206]: wlp3s0: carrier acquired > Sep 12 18:56:29 archonacer dhcpcd[206]: wlp3s0: IAID b9:79:57:96 > Sep 12 18:56:29 archonacer dhcpcd[206]: wlp3s0: soliciting an IPv6 router > Sep 12 18:56:30 archonacer dhcpcd[206]: wlp3s0: soliciting a DHCP lease > Sep 12 18:56:33 archonacer dhcpcd[206]: wlp3s0: offered 192.168.1.5 from > 192.168.1.1 `HG520c' > Sep 12 18:56:38 archonacer dhcpcd[206]: wlp3s0: leased 192.168.1.5 for > 86400 seconds > Sep 12 18:56:38 archonacer dhcpcd[206]: wlp3s0: adding route to > 192.168.1.0/24 > Sep 12 18:56:38 archonacer dhcpcd[206]: wlp3s0: adding default route via > 192.168.1.1 > Sep 12 18:56:41 archonacer dhcpcd[206]: wlp3s0: no IPv6 Routers available > > > DEVICE TYPE STATE CONNECTION > wlp3s0 wifi connecting (getting IP configuration) m00min > enp4s0f0 ethernet unavailable -- > lo loopback unmanaged -- > STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN > connecting none enabled enabled enabled enabled > > I am sending this mail from the "connecting" network. > Here is also the tray. > > > I can't figure out what's wrong. > > Regards, > > alam > > On 09/12/2014 01:24 AM, Dan Williams wrote: > > On Thu, 2014-09-11 at 19:10 +0300, Lampropoulos Anastasios wrote: > >> Hello there, > >> > >> I am using an Arch linux box without an environment but with Openbox as > >> window manager and tint2 panel. > >> > >> NetworkManager is my choice for controlling my network connections. > >> The network is operational and there is no functional problem. > >> The problem is about the icon of nm-applet in system tray. It remains in > >> a connecting state. > >> The tip informs me that my network is trying to request a wi-fi network > >> address but that's not true. > >> I believe that NetworkManager and nm-applet do not communicate properly > >> and nm-applet is never informed about nm' connected state. > >> BUT I don't know how to debug it or... > >> Could you please guide me? > > If you run "nmcli dev" and "nmcli gen" in a terminal, what do those > > report? That should tell you exactly what NetworkManager things is > > going on, and we can use that to figure out where the problem is. > > > > Dan > > > _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
