Network disconnects and then reconnects

English Network/Internet
1

The most recent update (20241006) seems to have caused some serious issues with network reliability. I notice the following from sudo journalctl -fu NetworkManager. The network reliability seems to impact the Ethernet (output below) and Wi-Fi connections. Thoughts? Thank you for your help with this.

Ethernet Card

$ lspci -nn | grep -i ethernet
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)

Output from Deactivating and Reactivating

$ sudo journalctl -fu NetworkManager
[sudo] password for root:
Oct 07 18:39:16 babel NetworkManager[1524]: <info>  [1728347956.7160] policy: set 'Wired connection 1' (enp4s0) as default for IPv6 routing and DNS
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.2849] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132, acd pending
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.4403] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.4406] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.5772] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.6072] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.6073] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.6076] manager: NetworkManager state is now CONNECTED_SITE
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.6079] device (enp4s0): Activation: successful, device activated.
Oct 07 18:39:17 babel NetworkManager[1524]: <info>  [1728347957.7541] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 07 18:43:10 babel NetworkManager[1524]: <info>  [1728348190.9962] audit: op="statistics" interface="enp4s0" ifindex=2 args="2000" pid=2184 uid=1000 result="success"
Oct 07 18:43:16 babel NetworkManager[1524]: <info>  [1728348196.6858] audit: op="statistics" interface="enp4s0" ifindex=2 args="2000" pid=2184 uid=1000 result="success"
Oct 07 18:43:17 babel NetworkManager[1524]: <info>  [1728348197.9158] audit: op="statistics" interface="enp4s0" ifindex=2 args="2000" pid=2184 uid=1000 result="success"
Oct 07 18:44:10 babel NetworkManager[1524]: <info>  [1728348250.5916] device (enp4s0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 07 18:44:10 babel NetworkManager[1524]: <info>  [1728348250.5916] dhcp4 (enp4s0): canceled DHCP transaction
Oct 07 18:44:10 babel NetworkManager[1524]: <info>  [1728348250.5917] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 07 18:44:10 babel NetworkManager[1524]: <info>  [1728348250.5917] dhcp4 (enp4s0): state changed no lease
Oct 07 18:44:10 babel NetworkManager[1524]: <info>  [1728348250.7939] manager: NetworkManager state is now DISCONNECTED
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1866] device (enp4s0): carrier: link connected
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1867] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1872] policy: auto-activating connection 'Wired connection 1' (fe567d9e-f7f1-3998-8975-291702fe75c8)
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1875] device (enp4s0): Activation: starting connection 'Wired connection 1' (fe567d9e-f7f1-3998-8975-291702fe75c8)
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1876] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1878] manager: NetworkManager state is now CONNECTING
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.1879] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.2008] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:15 babel NetworkManager[1524]: <info>  [1728348255.2011] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 07 18:44:21 babel NetworkManager[1524]: <info>  [1728348261.1245] policy: set 'Wired connection 1' (enp4s0) as default for IPv6 routing and DNS
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.5337] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.5407] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.5408] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.5410] manager: NetworkManager state is now CONNECTED_SITE
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.5413] device (enp4s0): Activation: successful, device activated.
Oct 07 18:44:22 babel NetworkManager[1524]: <info>  [1728348262.7120] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 07 18:44:24 babel NetworkManager[1524]: <info>  [1728348264.1491] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132, acd pending
Oct 07 18:44:24 babel NetworkManager[1524]: <info>  [1728348264.3069] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132
Oct 07 18:44:24 babel NetworkManager[1524]: <info>  [1728348264.3071] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 07 18:44:38 babel NetworkManager[1524]: <info>  [1728348278.2744] device (enp4s0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 07 18:44:38 babel NetworkManager[1524]: <info>  [1728348278.2745] dhcp4 (enp4s0): canceled DHCP transaction
Oct 07 18:44:38 babel NetworkManager[1524]: <info>  [1728348278.2745] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 07 18:44:38 babel NetworkManager[1524]: <info>  [1728348278.2745] dhcp4 (enp4s0): state changed no lease
Oct 07 18:44:38 babel NetworkManager[1524]: <info>  [1728348278.4773] manager: NetworkManager state is now DISCONNECTED
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8376] device (enp4s0): carrier: link connected
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8378] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8383] policy: auto-activating connection 'Wired connection 1' (fe567d9e-f7f1-3998-8975-291702fe75c8)
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8386] device (enp4s0): Activation: starting connection 'Wired connection 1' (fe567d9e-f7f1-3998-8975-291702fe75c8)
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8388] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8389] manager: NetworkManager state is now CONNECTING
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8391] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8510] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:42 babel NetworkManager[1524]: <info>  [1728348282.8513] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 07 18:44:46 babel NetworkManager[1524]: <info>  [1728348286.6806] policy: set 'Wired connection 1' (enp4s0) as default for IPv6 routing and DNS
Oct 07 18:44:47 babel NetworkManager[1524]: <info>  [1728348287.7075] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:47 babel NetworkManager[1524]: <info>  [1728348287.7149] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:47 babel NetworkManager[1524]: <info>  [1728348287.7150] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 07 18:44:47 babel NetworkManager[1524]: <info>  [1728348287.7153] manager: NetworkManager state is now CONNECTED_SITE
Oct 07 18:44:47 babel NetworkManager[1524]: <info>  [1728348287.7156] device (enp4s0): Activation: successful, device activated.
Oct 07 18:44:48 babel NetworkManager[1524]: <info>  [1728348288.8712] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 07 18:44:52 babel NetworkManager[1524]: <info>  [1728348292.2499] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132, acd pending
Oct 07 18:44:52 babel NetworkManager[1524]: <info>  [1728348292.4569] dhcp4 (enp4s0): state changed new lease, address=192.168.247.132
Oct 07 18:44:52 babel NetworkManager[1524]: <info>  [1728348292.4571] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
2

It means that the Ethernet connection did go down.

Good experiment is to unplug the Ethernet and check the log, do you see the same message?

My first thought is that this is a hardware/interference problem which has nothing to do with the recent update apart from happening about the same time.

1 Like
3

A lot of things were changing at the same time and this ended up being misdiagnosed on my end. What helped it w.r.t. Tumbleweed, though, is Snapper. I reverted to a previous state that I knew was good and it exhibited the same issue, which had me investigate elsewhere.

2 Likes
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.