You are not logged in.

#1 2020-08-16 09:18:05

ahvth
Member
Registered: 2020-08-16
Posts: 3

[Solved] Ethernet connection stuck getting IP configuration (nmcli)

An issue cropped up recently wherein I am unable to get an IP address on my ethernet interface using nmcli. I have no such issues when I use my wifi interface and the ethernet works fine in Windows.

The log below would indicate to me that it's requesting an IP and just not getting an answer, but I know the DHCP doesn't have issues as every other device, and even the wifi interface on the same machine get an IP without issue.

journalctl -xe NM_CONNECTION=c731ca2a-2ea4-4971-82f2-42ab58f9c0bb + NM_DEVICE=enp6s0

***

Aug 16 11:10:07 obsidian NetworkManager[431]: <info>  [1597569007.6940] device (enp6s0): Activation: starting connection 'eth0' (c731ca2a-2ea4-4971-82f2-42ab58f9c0bb)
Aug 16 11:10:07 obsidian NetworkManager[431]: <info>  [1597569007.6942] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 11:10:07 obsidian NetworkManager[431]: <info>  [1597569007.6945] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 11:10:07 obsidian NetworkManager[431]: <info>  [1597569007.6949] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 16 11:10:07 obsidian NetworkManager[431]: <info>  [1597569007.6950] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Aug 16 11:10:53 obsidian NetworkManager[431]: <warn>  [1597569053.0533] dhcp4 (enp6s0): request timed out
Aug 16 11:10:53 obsidian NetworkManager[431]: <info>  [1597569053.0534] dhcp4 (enp6s0): state changed unknown -> timeout
Aug 16 11:10:53 obsidian NetworkManager[431]: <info>  [1597569053.0534] device (enp6s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Aug 16 11:10:53 obsidian NetworkManager[431]: <warn>  [1597569053.0542] device (enp6s0): Activation: failed for connection 'eth0'
Aug 16 11:10:53 obsidian NetworkManager[431]: <info>  [1597569053.0544] device (enp6s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 16 11:10:53 obsidian NetworkManager[431]: <info>  [1597569053.0915] dhcp4 (enp6s0): canceled DHCP transaction
Aug 16 11:10:53 obsidian NetworkManager[431]: <info>  [1597569053.0915] dhcp4 (enp6s0): state changed timeout -> done

I tried changing over to dhcpcd as the dhcp client for nmcli, but whenever I try to start it I get:

systemctl status dhcpcd@enp6s0.service

***

● dhcpcd@enp6s0.service - dhcpcd on enp6s0
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2020-08-16 11:14:29 CEST; 51s ago
    Process: 4024 ExecStart=/usr/bin/dhcpcd -q -w enp6s0 (code=exited, status=1/FAILURE)

Aug 16 11:13:59 obsidian dhcpcd[4026]: enp6s0: IAID c2:74:db:9a
Aug 16 11:14:00 obsidian dhcpcd[4026]: enp6s0: soliciting a DHCP lease
Aug 16 11:14:29 obsidian dhcpcd[4026]: timed out
Aug 16 11:14:29 obsidian dhcpcd[4026]: timed out
Aug 16 11:14:29 obsidian dhcpcd[4026]: main: control_stop: No such file or directory
Aug 16 11:14:29 obsidian dhcpcd[4026]: main: control_stop: No such file or directory
Aug 16 11:14:29 obsidian dhcpcd[4026]: dhcpcd exited
Aug 16 11:14:29 obsidian systemd[1]: dhcpcd@enp6s0.service: Control process exited, code=exited, status=1/FAILURE
Aug 16 11:14:29 obsidian systemd[1]: dhcpcd@enp6s0.service: Failed with result 'exit-code'.
Aug 16 11:14:29 obsidian systemd[1]: Failed to start dhcpcd on enp6s0.

Any help would be appreciated smile

Last edited by ahvth (2020-09-28 08:38:51)

Offline

#2 2020-08-16 09:58:11

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 10,781

Re: [Solved] Ethernet connection stuck getting IP configuration (nmcli)

Welcome to the boards

That's not how you switch to dhcpcd as the client for nmcli (which isn't possible anymore anyway,  the dhcpcd plugin for NM broke with newer dhcpcd versions and the relevant plugin removed in the Arch package) and doing this, the way you are attempting to do it will lead to concurrent network services running which can lead to all sorts of weirdness so you should make sure that you are explicitly not doing that. If you want to try and switch NM's plugin anyway you can try: https://wiki.archlinux.org/index.php/Ne … HCP_client

However just from the outputs we have so far it seems that both NM and dhcpcd are in agreement over the issue when trying to manage the interface.  Which moves the likely culprit to the entity they have in common, which is the kernel and more specifically the kernel module that should be giving you access to this network interface.

So check your dmesg/journalctl -k on whether any errors are logged with regards to the module that's supposed to give you the network interface, maybe even try to downgrade the kernel to a known working version or so.

Offline

#3 2020-08-16 12:08:55

ahvth
Member
Registered: 2020-08-16
Posts: 3

Re: [Solved] Ethernet connection stuck getting IP configuration (nmcli)

Thanks for your reply.

Before anything, I disabled dhcpcd and reverted to using the internal nmcli dhcp client.

I noticed that there was indeed a kernel upgrade yesterday (when this stopped working), so I rolled back from 5.8.1 to 5.7.12.

However, this didn't resolve the issue, so I put back the newest kernel and checked the dmesg output for my Ethernet module (r8169):

[andrew@obsidian ~]$ journalctl -k | grep r8169
Aug 16 13:41:05 obsidian kernel: r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
Aug 16 13:41:05 obsidian kernel: libphy: r8169: probed
Aug 16 13:41:05 obsidian kernel: r8169 0000:06:00.0 eth0: RTL8168g/8111g, 70:85:c2:74:db:9a, XID 4c0, IRQ 33
Aug 16 13:41:05 obsidian kernel: r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Aug 16 13:41:05 obsidian kernel: r8169 0000:06:00.0 enp6s0: renamed from eth0
Aug 16 13:41:06 obsidian kernel: Generic FE-GE Realtek PHY r8169-600:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-600:00, irq=IGNORE)
Aug 16 13:41:06 obsidian kernel: r8169 0000:06:00.0 enp6s0: Link is Down
Aug 16 13:41:09 obsidian kernel: r8169 0000:06:00.0 enp6s0: Link is Up - 1Gbps/Full - flow control rx/tx
Aug 16 13:41:15 obsidian kernel: NETDEV WATCHDOG: enp6s0 (r8169): transmit queue 0 timed out

I interpreted

Aug 16 13:41:06 obsidian kernel: r8169 0000:06:00.0 enp6s0: Link is Down

as meaning the interface was not active, so I activated it using

ip link set enp6s0 up

and attempted to activate the ethernet connection again using

nmcli con up eth0

It failed again after hanging "getting IP configuration", but the log output was different somewhat:

Aug 16 13:49:10 obsidian NetworkManager[438]: <info>  [1597578550.0537] device (enp6s0): Activation: starting connection 'eth0' (c731ca2a-2ea4-4971-82f2-42ab58f9c0bb)
Aug 16 13:49:10 obsidian NetworkManager[438]: <info>  [1597578550.0539] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:10 obsidian NetworkManager[438]: <info>  [1597578550.0551] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:10 obsidian NetworkManager[438]: <info>  [1597578550.0564] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:10 obsidian NetworkManager[438]: <info>  [1597578550.0573] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5143] device (enp6s0): state change: ip-config -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5150] device (enp6s0): disconnecting for new activation request.
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5232] device (enp6s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5458] dhcp4 (enp6s0): canceled DHCP transaction
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5458] dhcp4 (enp6s0): state changed unknown -> done
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5474] device (enp6s0): Activation: starting connection 'eth0' (c731ca2a-2ea4-4971-82f2-42ab58f9c0bb)
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5491] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5499] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5506] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:11 obsidian NetworkManager[438]: <info>  [1597578551.5512] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Aug 16 13:49:57 obsidian NetworkManager[438]: <warn>  [1597578597.0511] dhcp4 (enp6s0): request timed out
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0511] dhcp4 (enp6s0): state changed unknown -> timeout
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0512] device (enp6s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Aug 16 13:49:57 obsidian NetworkManager[438]: <warn>  [1597578597.0539] device (enp6s0): Activation: failed for connection 'eth0'
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0546] device (enp6s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0747] dhcp4 (enp6s0): canceled DHCP transaction
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0747] dhcp4 (enp6s0): state changed timeout -> done
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0763] device (enp6s0): Activation: starting connection 'eth0' (c731ca2a-2ea4-4971-82f2-42ab58f9c0bb)
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0764] device (enp6s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0768] device (enp6s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0772] device (enp6s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 16 13:49:57 obsidian NetworkManager[438]: <info>  [1597578597.0775] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)

I don't really see any useful information here that could help me get to the root of the issue. It looks like it retries and just cannot get a response from the dhcp server, but what I don't understand is how this could be an issue with 2 separate routers that also incidentally work with every other device and interface, and indeed this very same interface under Windows (and I assume it would work under a livecd as well).

Last edited by ahvth (2020-08-16 12:11:05)

Offline

#4 2020-09-28 08:37:22

ahvth
Member
Registered: 2020-08-16
Posts: 3

Re: [Solved] Ethernet connection stuck getting IP configuration (nmcli)

I'm sorry for not posting this sooner, but the issue here is likely related to the dual-boot configuration I was using at the time. It appears that windows authorizes itself to modify device firmware outside of its own scope, which made the device incompatible with the Linux driver.

The solution here was to buy a new network card and remove the windows installation.

Offline

Board footer

Powered by FluxBB