You are not logged in.
I've been running Arch on my laptop for around a year now and never had any issues, however from the last few days I am having an issue where the Wifi works fine but Ethernet refuses to activate in NetworkManager and I'm stumped as to what the problem is. The only upgrade I notice that could affect it was the kernel upgrade to 5.15.6 but I tried rolling it back to 5.15.5 with no luck.
I'm using a Realtek RTL8153 2.5 Gb dongle attached to a Pluggable Thunderbolt 3 dock. It doesn't seem to be a Realtek issue since plugging it directly into the ethernet on the Pluggable dock has the same issue. As well using the dongle directly with the laptop makes no difference either.
In journalctl -xe I see the following sequence when it tries to activate the network connection
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.2998] device (enp47s0u1u2c2): Activation: starting connection 'Wired connection 1' (96eba48e-175a-3fc9-b245-79becd0fbf69)
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.2999] audit: op="connection-activate" uuid="96eba48e-175a-3fc9-b245-79becd0fbf69" name="Wired connection 1" pid=1227 uid=1000 result="success"
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.2999] device (enp47s0u1u2c2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.3001] device (enp47s0u1u2c2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.3003] device (enp47s0u1u2c2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.3005] dhcp4 (enp47s0u1u2c2): activation: beginning transaction (timeout in 45 seconds)
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <warn> [1638820296.6832] dhcp4 (enp47s0u1u2c2): request timed out
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.6832] dhcp4 (enp47s0u1u2c2): state changed unknown -> timeout
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.6833] device (enp47s0u1u2c2): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <warn> [1638820296.6839] device (enp47s0u1u2c2): Activation: failed for connection 'Wired connection 1'
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.6841] device (enp47s0u1u2c2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7331] dhcp4 (enp47s0u1u2c2): canceled DHCP transaction
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7332] dhcp4 (enp47s0u1u2c2): state changed timeout -> terminated
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7354] policy: auto-activating connection 'Wired connection 1' (96eba48e-175a-3fc9-b245-79becd0fbf69)
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7365] device (enp47s0u1u2c2): Activation: starting connection 'Wired connection 1' (96eba48e-175a-3fc9-b245-79becd0fbf69)
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7368] device (enp47s0u1u2c2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7373] device (enp47s0u1u2c2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7380] device (enp47s0u1u2c2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.7385] dhcp4 (enp47s0u1u2c2): activation: beginning transaction (timeout in 45 seconds)I am using dnsmasq to manage some internal addresses and it is running just fine:
$ ps -ef | grep dns
nobody 1162 746 0 08:26 ? 00:00:00 /usr/bin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=400 --clear-on-reload --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
root 4633 4610 0 08:51 pts/0 00:00:00 grep dnsMy resolv.conf as as follows:
# Generated by NetworkManager
nameserver 127.0.0.1
options edns0 trust-adThanks for any pointers as I'm a bit stumped.
Last edited by gnunn (2021-12-08 03:14:09)
Offline
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.3005] dhcp4 (enp47s0u1u2c2): activation: beginning transaction (timeout in 45 seconds)
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <warn> [1638820296.6832] dhcp4 (enp47s0u1u2c2): request timed out
Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.6832] dhcp4 (enp47s0u1u2c2): state changed unknown -> timeoutYou're not getting a lease from the router.
"Have you tried turning it off and on again?™" (ie. the router)
Otherwise try a different dhcp client, https://wiki.archlinux.org/title/Networ … HCP_client
Offline
Dec 06 11:50:51 gnunn-book13 NetworkManager[761]: <info> [1638820251.3005] dhcp4 (enp47s0u1u2c2): activation: beginning transaction (timeout in 45 seconds) Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <warn> [1638820296.6832] dhcp4 (enp47s0u1u2c2): request timed out Dec 06 11:51:36 gnunn-book13 NetworkManager[761]: <info> [1638820296.6832] dhcp4 (enp47s0u1u2c2): state changed unknown -> timeoutYou're not getting a lease from the router.
"Have you tried turning it off and on again?™" (ie. the router)Otherwise try a different dhcp client, https://wiki.archlinux.org/title/Networ … HCP_client
Rebooted the router and made no difference. However my laptop, along with a server and a NAS, are plugged into a QNAP 2.5 Gb switch which is then plugged into the Asus router. Plugging the laptop directly into the Asus works fine, though it drops me down to 1Gb, so something going on with the switch however it's weird everything else works fine.
I'll do some investigation since it looks like a hardware issue of some sort.
Offline
Re-starting the switch a second time seems to have fixed it, thanks.
Offline