Arch Linux

Lehthanis

Member

Registered: 2013-09-26

Posts: 21

NetworkManager suddenly stuck at connecting (getting IP configuration)

Hi all, just did a pacman -Syu this morning after a week or so of not using the machine...There were a few updates to include a new kernel 3.15.8-1 I think...And of course the xorg116...which I had to avoid due to catalyst drivers...so I added the xorg115 repo at the top and it skipped 116...no problem...the only other odd thing was to replace lzo2 with lzo, which I allowed...

Now I've rebooted, and NetworkManager is stuck on "connecting (getting IP configuration)" according to nmcli d

Anything new I should be aware of? Anyone have any idea what I can try to get wired connectivity back? (I have no wifi where I am now).

fungle

Member

Registered: 2014-05-01

Posts: 81

Re: NetworkManager suddenly stuck at connecting (getting IP configuration)

Run

 journalctl -f 

and then try connecting with NetworkManager and post the output.
But I'm going to take a shot at what might be the issue. Have you tried disabling IPv6 settings? Go to Edit Settings from NetworkManager, select the connection to edit, go to the IPv6 Settings tab, and select Ignore from the Method drop-down menu. Sometimes NetworkManager times out trying to connect IPv6 when there isn't any.

Lehthanis

Member

Registered: 2013-09-26

Posts: 21

Re: NetworkManager suddenly stuck at connecting (getting IP configuration)

I don't have the applet installed, I'm on a console WM (DWM) so I need to be able to do this using I guess nmcli (which is how I usually interact with networkmanager)...

It doesn't appear to be hanging on ipv6...I get the ipv6 timeout about 30 seconds after I start up the connection...then it starts up stage 4 of 5 (IPv4 Configure Timeout) which goes through scheduled, then started, then complete...and thats the last thing I see.  Here's the output.

enp6s0 is the one I'm trying to connect.  This is the output to journalctl -f when I run nmcli n on

Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> enable requested (sleeping: no  enabled: no)
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> re-enabling...
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (enp6s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (enp6s0): preparing device
Aug 15 07:37:03 archnemesis kernel: r8169 0000:06:00.0 enp6s0: link down
Aug 15 07:37:03 archnemesis kernel: r8169 0000:06:00.0 enp6s0: link down
Aug 15 07:37:03 archnemesis kernel: IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0): preparing device
Aug 15 07:37:03 archnemesis kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> NetworkManager state is now DISCONNECTED
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0) supports 4 scan SSIDs
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0): supplicant interface state: starting -> ready
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
Aug 15 07:37:03 archnemesis NetworkManager[206]: <info> (wlp2s0) supports 4 scan SSIDs
Aug 15 07:37:04 archnemesis NetworkManager[206]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
Aug 15 07:37:05 archnemesis kernel: r8169 0000:06:00.0 enp6s0: link up
Aug 15 07:37:05 archnemesis kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): link connected
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Auto-activating connection 'Ethernet connection 1'.
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) starting connection 'Ethernet connection 1'
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 1 of 5 (Device Prepare) started...
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> NetworkManager state is now CONNECTING
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 2 of 5 (Device Configure) scheduled...
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 1 of 5 (Device Prepare) complete.
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 2 of 5 (Device Configure) starting...
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): device state change: prepare -> config (reason 'none') [40 50 0]
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 2 of 5 (Device Configure) successful.
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 2 of 5 (Device Configure) complete.
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 3 of 5 (IP Configure Start) started...
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> dhcpcd started with pid 3027
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 3 of 5 (IP Configure Start) complete.
Aug 15 07:37:05 archnemesis dhcpcd[3027]: version 6.4.3 starting
Aug 15 07:37:05 archnemesis NetworkManager[206]: dhcpcd[3027]: version 6.4.3 starting
Aug 15 07:37:05 archnemesis NetworkManager[206]: <info> (enp6s0): DHCPv4 state changed nbi -> preinit
Aug 15 07:37:05 archnemesis NetworkManager[206]: dhcpcd[3027]: DUID 00:01:00:01:19:f4:f6:f1:00:8c:fa:49:42:90
Aug 15 07:37:05 archnemesis dhcpcd[3027]: DUID 00:01:00:01:19:f4:f6:f1:00:8c:fa:49:42:90
Aug 15 07:37:05 archnemesis NetworkManager[206]: dhcpcd[3027]: enp6s0: IAID fa:49:42:90
Aug 15 07:37:05 archnemesis dhcpcd[3027]: enp6s0: IAID fa:49:42:90
Aug 15 07:37:05 archnemesis dhcpcd[3027]: enp6s0: soliciting an IPv6 router
Aug 15 07:37:05 archnemesis NetworkManager[206]: dhcpcd[3027]: enp6s0: soliciting an IPv6 router
Aug 15 07:37:06 archnemesis dhcpcd[3027]: enp6s0: soliciting a DHCP lease
Aug 15 07:37:06 archnemesis NetworkManager[206]: dhcpcd[3027]: enp6s0: soliciting a DHCP lease
Aug 15 07:37:07 archnemesis ntpd[288]: Listen normally on 7 enp6s0 [fe80::28c:faff:fe49:4290%2]:123
Aug 15 07:37:07 archnemesis ntpd[288]: new interface(s) found: waking up resolver
Aug 15 07:37:18 archnemesis dhcpcd[3027]: enp6s0: no IPv6 Routers available
Aug 15 07:37:18 archnemesis NetworkManager[206]: dhcpcd[3027]: enp6s0: no IPv6 Routers available
Aug 15 07:37:35 archnemesis dhcpcd[3027]: timed out
Aug 15 07:37:35 archnemesis dhcpcd[3027]: exited
Aug 15 07:37:35 archnemesis NetworkManager[206]: dhcpcd[3027]: timed out
Aug 15 07:37:35 archnemesis NetworkManager[206]: dhcpcd[3027]: exited
Aug 15 07:37:35 archnemesis NetworkManager[206]: <info> (enp6s0): DHCPv4 client pid 3027 exited with status 1
Aug 15 07:37:35 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Aug 15 07:37:35 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Aug 15 07:37:35 archnemesis NetworkManager[206]: <info> Activation (enp6s0) Stage 4 of 5 (IPv4 Configure Timeout) complete.

Last edited by Lehthanis (2014-08-15 12:49:02)

fungle

Member

Registered: 2014-05-01

Posts: 81

Re: NetworkManager suddenly stuck at connecting (getting IP configuration)

It looks like dhcpd is timing out after trying ipv6 and then just exiting instead of falling back to trying ipv4. Try adding these lines to your /etc/dhcpcd.conf:

ipv4only
nodhcp6
noipv6
noipv6rs

`man dhcpcd.conf` for more info on these options. Also you can add the debug option for more verbosity from dhcpcd to your journal logs.

Lehthanis

Member

Registered: 2013-09-26

Posts: 21

Re: NetworkManager suddenly stuck at connecting (getting IP configuration)

Resurrecting this old topic because I never got it fixed. I did add the above to my dhcpcd.conf, but it didn't fix it.  It's still stuck on getting ip address...but I did discover it's only happening on the network at work.  I can plug it in wired at home, and it works fine, but when I connect it at work, it does this.

Now before anyone suggests that work may be blocking the connection on purpose, I must explain the network.  We have a separate cable internet connection at work for engineers that basically is designed to allow us to have free access to the internet without all the restrictions of the actual work network. I've already talked to the IT guy, and he says he's doing nothing to the router that would alter the way linux would connect...he doesn't even know linux or anything about it. So it's a default router setup.

I have windows installed dual boot on this machine, and wired connection works fine on this same network on this same machine in windows.

Lastly, the only major change recently is that the office I work in changed from a Netgear prosafe 8 port gigabit switch (GS108) to a Netgear GS724TS that was considered "Extra" so we took it because we needed the extra ports.  It's been reset to factory default, and doesn't do anything fancy...But if there's something I can check in the switch that would mess up my connection, I'll gladly do it.  Any thoughts?

Lehthanis

Member

Registered: 2013-09-26

Posts: 21

Re: NetworkManager suddenly stuck at connecting (getting IP configuration)

Update...it's definitely the 24 port switch causing the problem...I tried removing it from the loop and going back to the basic 8 port, and it connected immediately.  What setting on the 24 port switch would prevent arch from connecting?