You are not logged in.

#1 2025-10-11 22:29:46

Piripe
Member
Registered: 2025-10-10
Posts: 4

Weird network disconnections

I installed Arch with Hyprland 3 months ago and I have a weird issue with my network...
I'm using NetworkManager with 2 network cards (only using the second one) Intel Corporation Ethernet Connection (7) I219-V and Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
Since I installed Arch, I get random disconnection for a few seconds each time. (When I'm on a Discord voice call it's like... Disconnected... (2 seconds) No Route... (2 seconds) RTC Connection... (5 seconds) Connected)
Most of the time, it's between 7 PM and 12 AM (Before and after, I don't have any problem)
Sometimes I can be in a voice chat on Discord for the entire day, having no disconnection between 12PM and 6PM, then getting disconnected 6 times at 7PM for no reason (not doing anything different)

Note: I'm using Discord as example because it's the worst case, I'm talking and... [Disconnected] Pretty frustrating. But when I get disconnected on Discord, my browser can't load pages too, I actually don't have internet.

I tried multiple things to fix/debug that:
- I installed the r8125 driver from AUR and blacklisted the r8169
- I added the "pcie_aspm=off" kernel parameter
- I disabled a power saving options related to the network (tso off gso off gro off)
- I tried both network controllers (and also both at the same time xD) but I have the same issue
- No log in journalctl related to a network crash, disconnection, reconnection or anything else
- Some day I managed to run "nmcli device status" during the network disconnection and seen that the port was still connected (?)
- I don't have any disconnection on my phone (with wifi) and never got a similar issue before switching to Arch
- I switched from NetworkManager over to systemd-networkd and I have the same issue

Offline

#2 2025-10-11 23:08:16

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,058

Re: Weird network disconnections

No log in journalctl related to a network crash, disconnection, reconnection or anything else … I actually don't have internet.

Next time this happens check

ping -c3 _gateway
ping -c3 8.8.8.8
ping -c3 google.com

to identify whether this is a LAN, WAN or DNS issue.

Online

#3 2025-10-12 18:22:18

Piripe
Member
Registered: 2025-10-10
Posts: 4

Re: Weird network disconnections

I only got the time to ping the gateway, and the LAN is not working

Offline

#4 2025-10-12 20:20:35

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,058

Re: Weird network disconnections

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855 - what is the actual error you get from ping?
Also please post your complete system journal for a boot after such loss:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Online

#5 2025-10-13 10:09:35

Piripe
Member
Registered: 2025-10-10
Posts: 4

Re: Weird network disconnections

Sorry for the lack of details from the last post, it's because my pc was highly loaded (Blender rendering) and it crashed before I got the time to reply to you.

I'm gonna explain a bit of my local network setup... My PC is connected to a switch, which has 2 devices connected on it (My own computer and my homelab (192.168.1.70) that's why I tried to ping 192.168.1.70

So I ran these pings in order...

Piripe-PC% ping -c3 _gateway
PING _gateway (192.168.1.254) 56(84) bytes of data.

--- _gateway ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2058ms
Piripe-PC% ping -c3 192.168.1.70
PING 192.168.1.70 (192.168.1.70) 56(84) bytes of data.
64 bytes from 192.168.1.70: icmp_seq=1 ttl=64 time=0.195 ms
64 bytes from 192.168.1.70: icmp_seq=2 ttl=64 time=0.203 ms
64 bytes from 192.168.1.70: icmp_seq=3 ttl=64 time=0.188 ms

--- 192.168.1.70 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2079ms
rtt min/avg/max/mdev = 0.188/0.195/0.203/0.006 ms
Piripe-PC% ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2046ms
Piripe-PC% ping -c3 google.com
PING google.com (216.58.213.78) 56(84) bytes of data.
64 bytes from lhr25s01-in-f78.1e100.net (216.58.213.78): icmp_seq=1 ttl=114 time=11.5 ms
64 bytes from lhr25s01-in-f78.1e100.net (216.58.213.78): icmp_seq=2 ttl=114 time=11.3 ms
64 bytes from lhr25s01-in-f78.1e100.net (216.58.213.78): icmp_seq=3 ttl=114 time=11.8 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 11.274/11.532/11.797/0.213 ms

(The ping of google.com was probably after the reconnection)

And there is my journalctl (~10 seconds after the reconnection)
https://0x0.st/KSZs.txt

Offline

#6 2025-10-13 13:31:48

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 69,058

Re: Weird network disconnections

There's no indication of anything in the journal…
The _gateway is the switch w/ the two nodes or something behind that (your modemrouterswitchdhcpdnsserver)?
Can you still "ping 192.168.1.70" when the network is down and what do ethtool (takes the network device as parameter eg. eth0) and "ip a" report at this moment?
Can you bypass that switch for a while to see whether the network then remains stable?

Online

#7 2025-10-14 08:27:47

Piripe
Member
Registered: 2025-10-10
Posts: 4

Re: Weird network disconnections

My gateway is something behind the switch.

I disconnected the ethernet cable of my switch to get these outputs (It's not during a "normal" network loss):

Piripe-PC% ping -c3 google.com
ping: google.com: Temporary failure in name resolution
Piripe-PC% ping -c3 192.168.1.70
PING 192.168.1.70 (192.168.1.70) 56(84) bytes of data.
64 bytes from 192.168.1.70: icmp_seq=1 ttl=64 time=0.241 ms
64 bytes from 192.168.1.70: icmp_seq=2 ttl=64 time=0.159 ms
64 bytes from 192.168.1.70: icmp_seq=3 ttl=64 time=0.260 ms

--- 192.168.1.70 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2064ms
rtt min/avg/max/mdev = 0.159/0.220/0.260/0.043 ms
Piripe-PC% sudo ethtool enp4s0
[sudo] password for piripe: 
Settings for enp4s0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                       100baseT/Half 100baseT/Full
	                       1000baseT/Full
	                       2500baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                       100baseT/Half 100baseT/Full
	                       1000baseT/Full
	                       2500baseT/Full
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                    100baseT/Half 100baseT/Full
	                                    1000baseT/Full
	                                    2500baseT/Full
	Link partner advertised pause frame use: Symmetric Receive-only
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 2500Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	MDI-X: on
	Supports Wake-on: pumbg
	Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
	Link detected: yes
Piripe-PC% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b0:19:21:6c:20:a3 brd ff:ff:ff:ff:ff:ff
    altname enxb019216c20a3
    inet 192.168.1.105/24 brd 192.168.1.255 scope global enp4s0
       valid_lft forever preferred_lft forever
    inet6 fe80::b219:21ff:fe6c:20a3/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 04:d4:c4:8d:b7:4c brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    altname enx04d4c48db74c
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc htb state DOWN group default qlen 1000
    link/ether 52:54:00:58:bd:5e brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
    altname enx005056c00001
    inet 192.168.95.1/24 brd 192.168.95.255 scope global vmnet1
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:1/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
6: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
    altname enx005056c00008
    inet 172.16.50.1/24 brd 172.16.50.255 scope global vmnet8
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fec0:8/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

I'll try to connect my computer without the switch, I'll update you in the next post if it's more stable or not

Offline

Board footer

Powered by FluxBB