Ethernet keeps getting deactivated and reactivating after a second

Hello, I’m new to Endeavor and everything is going well except for this recurring issue that I can’t seem to get rid of. Every time I try to load a webpage, join a Discord call, or do anything else that uses my internet, it will deactivate itself, reactivate itself a second later, and repeat the process three or four times before working for a few minutes before doing it again. I have no idea what to do.

For starters, you can post the journal logs.

$ journalctl -b 0 | eos-sendlog

So I ran the command and here is the link for the paste bin https://0x0.st/Hn1A.txt

These don’t seem to be the logs for the problematic boot. These look like the logs you got after a fresh reboot, when the problem has yet to occur.

Did the problem occur in the previous boot?

Try:

$ journalctl -b 1 | eos-sendlog

Or

$ journalctl -b 2 | eos-sendlog

Yes it was the 14th I think I found the correct boot log after running the command a few times https://0x0.st/Hn1u.txt

I have this issue with my LAN. I use a USB LAN card and it sometimes does this. I just unplug and plug it in. Then all is fine. Try disabling and enabling the problematic LAN interface.

You can use the terminal.

To disable.
ip link set dev <interface name> down

To enable.
ip link set dev <interface name> up

To list interfaces.
ip link show

These seem to indicate the problem:

Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4187] device (enp4s0): carrier: link connected
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4190] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Feb 14 21:28:00 Alfredo-Endeavouros kernel: Generic FE-GE Realtek PHY r8169-0-400:00: Downshift occurred from negotiated speed 1Gbps to actual speed 100Mbps, check cabling!
Feb 14 21:28:00 Alfredo-Endeavouros kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 100Mbps/Full (downshifted) - flow control off
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4196] policy: auto-activating connection 'Wired connection 2' (7e170ce1-da6d-392f-b0e5-b1832a571bd3)
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4200] device (enp4s0): Activation: starting connection 'Wired connection 2' (7e170ce1-da6d-392f-b0e5-b1832a571bd3)
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4201] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4204] manager: NetworkManager state is now CONNECTING
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4205] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4366] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 14 21:28:00 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967680.4370] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 14 21:28:00 Alfredo-Endeavouros avahi-daemon[703]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::6433:e099:475:e4b8.
Feb 14 21:28:02 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967682.4298] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 14 21:28:02 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967682.4303] policy: set 'Wired connection 2' (enp4s0) as default for IPv6 routing and DNS
Feb 14 21:28:02 Alfredo-Endeavouros avahi-daemon[703]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::6433:e099:475:e4b8.
Feb 14 21:28:02 Alfredo-Endeavouros avahi-daemon[703]: Joining mDNS multicast group on interface enp4s0.IPv6 with address 2600:1702:1a80:4dd0:1952:67cc:55fc:5370.
Feb 14 21:28:02 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967682.4365] dhcp6 (enp4s0): state changed new lease, address=2600:1702:1a80:4dd0::16
Feb 14 21:28:02 Alfredo-Endeavouros avahi-daemon[703]: Registering new address record for 2600:1702:1a80:4dd0:1952:67cc:55fc:5370 on enp4s0.*.
Feb 14 21:28:02 Alfredo-Endeavouros avahi-daemon[703]: Withdrawing address record for fe80::6433:e099:475:e4b8 on enp4s0.
Feb 14 21:28:02 Alfredo-Endeavouros avahi-daemon[703]: Registering new address record for 2600:1702:1a80:4dd0::16 on enp4s0.*.
Feb 14 21:28:03 Alfredo-Endeavouros systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 14 21:28:04 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967684.3717] dhcp4 (enp4s0): state changed new lease, address=192.168.1.152
Feb 14 21:28:04 Alfredo-Endeavouros NetworkManager[750]: <info>  [1707967684.3720] policy: set 'Wired connection 2' (enp4s0) as default for IPv4 routing and DNS

This issue, which will occur every time the dhcp server renews the lease, is well-documented in the Arch Wiki. The solution proposed in the Arch Wiki is to manually restart the network adapter. E.g:

# ip link set dev enp4s0 down
# ip link set dev enp4s0 up

However, I don’t really like this approach (it seems a bit hackish to me). On another note, some users experiencing the same issue have reported that replacing the ethernet cable resolved the issue.

1 Like

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