Network connection fails randomly

rKJ9Db · January 22, 2022, 12:47am

Hello,

I am struggling with network issues since a few months. Every few times (sometimes daily) I get a complete network disconnect. I cannot even ping my router anymore. Only physically replugging the network cable or restarting the computer helps.

I had an extensive thread over at the Manjaro forums, since that is what I was using before. Unfortuanetly I did not get anymore replies anymore and pushing threads is not allowed - so I decided to just wipe my system and start clean on EndeavourOS.

And here I am, and the same issue appeared again I really hoped some misconfiguration borked my Manjaro install, but since it’s happening on a fresh install of EndeavourOS (GNOME) it must be some sort of kernel / hardware thing?

A bit more information:

logs are seeminly random, no pattern, different every time
restarting NetworkManager or systemd-resolved does not help
disabling IPv6 or DNSSEC does not help
setting a DNS or none → no difference
static IP vs DHCP → no difference
issue appears on kernel 5.10, 5.14, 5.15 and 5.16
works flawlessly on Windows (I am dual booting but fastboot is disabled)
worked flawlessly on Manjaro for several months last year, the issues appeared ~3 months ago

And some logs, collected on the old Manjaro system (I could not collect enough logs on EndeavourOS yet since the issue only happend once since I installed the system a few days ago):

journalctl -since="2 minutes ago"

-- Journal begins at Thu 2021-12-02 15:27:38 CET, ends at Tue 2021-12-14 14:43:35 CET. --
Dez 14 14:41:55 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:41:55 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.23' (uid=1000 pid=1853 comm="/usr/bin/gnome-shell ")
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Activating service name='org.gnome.Nautilus' requested by ':1.23' (uid=1000 pid=1853 comm="/usr/bin/gnome-shell ")
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Successfully activated service 'org.gnome.Nautilus'
Dez 14 14:42:04 manjaro nautilus[9051]: Connecting to org.freedesktop.Tracker3.Miner.Files
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Activating service name='org.gnome.gedit' requested by ':1.23' (uid=1000 pid=1853 comm="/usr/bin/gnome-shell ")
Dez 14 14:42:04 manjaro dbus-daemon[1779]: [session uid=1000 pid=1779] Successfully activated service 'org.gnome.gedit'
Dez 14 14:42:05 manjaro gnome-shell[1853]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x55894714a370] is on because it needs an allocation.
Dez 14 14:42:05 manjaro gnome-shell[1853]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5589488c0350] is on because it needs an allocation.
Dez 14 14:42:05 manjaro gnome-shell[1853]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5589521494d0] is on because it needs an allocation.
Dez 14 14:42:08 manjaro systemd-resolved[734]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 9.9.9.9.
Dez 14 14:42:08 manjaro systemd-resolved[734]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 9.9.9.9.
Dez 14 14:42:17 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:42:17 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:19 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:01:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=58736 DF PROTO=2 
Dez 14 14:42:22 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:42:22 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:25 manjaro systemd-resolved[734]: Using degraded feature set TCP instead of UDP for DNS server 9.9.9.9.
Dez 14 14:42:25 manjaro systemd-resolved[734]: Using degraded feature set TCP instead of UDP for DNS server 9.9.9.9.
Dez 14 14:42:38 manjaro spotify.desktop[2175]: [2021/12/14 14:42:38:3911] ERR: getaddrinfo failed: -2
Dez 14 14:42:38 manjaro gnome-shell[1853]: Failed to get met.no forecast data: 7 Could not connect: Socket I/O timed out
Dez 14 14:42:40 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:42:40 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:43 manjaro systemd-resolved[734]: Using degraded feature set UDP instead of TCP for DNS server 9.9.9.9.
Dez 14 14:42:48 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:42:48 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:49 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:42:49 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:42:54 manjaro spotify.desktop[2175]: [2021/12/14 14:42:54:9244] ERR: getaddrinfo failed: -2
Dez 14 14:42:56 manjaro systemd-resolved[734]: Using degraded feature set TCP instead of UDP for DNS server 9.9.9.9.
Dez 14 14:43:00 manjaro systemd-resolved[734]: Using degraded feature set UDP instead of TCP for DNS server 9.9.9.9.
Dez 14 14:43:06 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:06 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:06 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:06 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:07 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:07 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:07 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:07 manjaro rtkit-daemon[1473]: Supervising 10 threads of 4 processes of 1 users.
Dez 14 14:43:13 manjaro systemd-resolved[734]: Using degraded feature set TCP instead of UDP for DNS server 9.9.9.9.
Dez 14 14:43:26 manjaro spotify.desktop[2175]: [2021/12/14 14:43:26:6321] ERR: getaddrinfo failed: -2
Dez 14 14:43:26 manjaro gnome-shell[1853]: Failed to get met.no forecast data: 2 Error resolving “aa037rv1tsaszxi6o.api.met.no”: Name or service not known
Dez 14 14:43:26 manjaro gnome-shell[1853]: Could not load a pixbuf from icon theme.
                                                    This may indicate that pixbuf loaders or the mime database could not be found.
Dez 14 14:43:31 manjaro systemd-resolved[734]: Using degraded feature set UDP instead of TCP for DNS server 9.9.9.9.
Dez 14 14:43:34 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 14 14:43:34 manjaro gnome-shell[1853]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 14 14:43:35 manjaro systemd[1757]: Started Application launched by gsd-media-keys.
Dez 14 14:43:35 manjaro systemd[1757]: Started VTE child process 9449 launched by gnome-terminal-server process 6961.

journalctl -g enp39s0 At 09:12:44 I unplugged my network cable and replugged 3 seconds later. Then the connection was back.

-- Journal begins at Thu 2021-12-02 16:36:14 CET, ends at Tue 2021-12-21 11:43:08 CET. --
Dez 21 08:56:35 manjaro kernel: r8169 0000:27:00.0 enp39s0: renamed from eth0
Dez 21 08:56:36 manjaro NetworkManager[1041]: <info>  [1640073396.9923] manager: (enp39s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dez 21 08:56:36 manjaro NetworkManager[1041]: <info>  [1640073396.9927] device (enp39s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dez 21 08:56:37 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Down
Dez 21 08:56:40 manjaro NetworkManager[1041]: <info>  [1640073400.0726] device (enp39s0): carrier: link connected
Dez 21 08:56:40 manjaro NetworkManager[1041]: <info>  [1640073400.0728] device (enp39s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dez 21 08:56:40 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Up - 1Gbps/Full - flow control off
Dez 21 08:56:40 manjaro kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp39s0: link becomes ready
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1832] device (enp39s0): Activation: starting connection 'Home LAN' (67bd96cc-0668-3034-aada-77f2515ceeef)
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1833] device (enp39s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1836] device (enp39s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1842] device (enp39s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1844] dhcp4 (enp39s0): activation: beginning transaction (timeout in 45 seconds)
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1916] dhcp4 (enp39s0): state changed unknown -> bound, address=192.168.10.90
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1923] device (enp39s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1946] device (enp39s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1947] device (enp39s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1951] policy: set 'Home LAN' (enp39s0) as default for IPv4 routing and DNS
Dez 21 08:56:46 manjaro NetworkManager[1041]: <info>  [1640073406.1962] device (enp39s0): Activation: successful, device activated.
Dez 21 08:56:46 manjaro systemd-resolved[700]: enp39s0: Bus client set default route setting: yes
Dez 21 08:56:46 manjaro systemd-resolved[700]: enp39s0: Bus client set DNS server list to: 192.168.10.10, 1.1.1.1, 9.9.9.9
Dez 21 08:56:46 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=54268 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 08:56:46 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=54300 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 08:56:46 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=54362 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 08:56:47 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:fc:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=1 ID=58162 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 09:10:50 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:44:1c:a8:8a:bb:e3:08:00 SRC=192.168.10.127 DST=192.168.10.90 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=58345 DF PROTO=UDP SPT=53658 DPT=54001 LEN=524 
Dez 21 09:10:50 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:b0:e4:d5:c7:4e:3b:08:00 SRC=192.168.10.109 DST=192.168.10.90 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=44832 DF PROTO=UDP SPT=53549 DPT=54001 LEN=524 
Dez 21 09:11:08 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:01:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=24220 DF PROTO=2 
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.099014:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.103162:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.103288:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.115647:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.122714:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.129997:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.134844:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.134907:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.134945:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.134991:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135027:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135056:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135153:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135217:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135267:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135319:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135366:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135396:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135439:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135475:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135502:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135529:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135555:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135594:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135619:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135647:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135672:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135697:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135723:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135749:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135773:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135799:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135826:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.135887:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.137006:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140305:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140369:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140404:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140452:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140483:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140510:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140537:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140576:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:11:48 manjaro gnome-shell[4961]: [4961:35:1221/091148.140604:ERROR:port.cc(371)] Port[4e12200:0:1:0:local:Net[enp39s0:192.168.10.x/24:Ethernet:id=1]]: Received non-STUN packet from unknown address: 52.112.218.x:3480
Dez 21 09:12:44 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Down
Dez 21 09:12:47 manjaro NetworkManager[1041]: <info>  [1640074367.8893] device (enp39s0): carrier: link connected
Dez 21 09:12:47 manjaro NetworkManager[1041]: <info>  [1640074367.8894] device (enp39s0): DHCPv4 lease renewal requested
Dez 21 09:12:47 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Up - 1Gbps/Full - flow control off
Dez 21 09:12:47 manjaro NetworkManager[1041]: <info>  [1640074367.9086] dhcp4 (enp39s0): canceled DHCP transaction
Dez 21 09:12:47 manjaro NetworkManager[1041]: <info>  [1640074367.9087] dhcp4 (enp39s0): state changed bound -> terminated
Dez 21 09:12:47 manjaro NetworkManager[1041]: <info>  [1640074367.9088] dhcp4 (enp39s0): activation: beginning transaction (timeout in 45 seconds)
Dez 21 09:12:47 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=50934 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 09:12:48 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=51007 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 09:12:48 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=51016 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 09:12:48 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:fc:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=1 ID=34465 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 21 09:12:49 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:44:1c:a8:8a:bb:e3:08:00 SRC=192.168.10.127 DST=192.168.10.90 LEN=162 TOS=0x00 PREC=0x00 TTL=64 ID=40751 DF PROTO=TCP SPT=8009 DPT=35416 WINDOW=1425 RES=0x00 ACK PSH URGP=0 
Dez 21 09:12:49 manjaro NetworkManager[1041]: <info>  [1640074369.9168] dhcp4 (enp39s0): state changed unknown -> bound, address=192.168.10.90
Dez 21 09:12:50 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:44:1c:a8:8a:bb:e3:08:00 SRC=192.168.10.127 DST=192.168.10.90 LEN=186 TOS=0x00 PREC=0x00 TTL=64 ID=40757 DF PROTO=TCP SPT=8009 DPT=35416 WINDOW=1425 RES=0x00 ACK PSH FIN URGP=0 
Dez 21 09:12:51 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:98:9b:cb:0d:b5:33:08:00 SRC=52.114.78.128 DST=192.168.10.90 LEN=92 TOS=0x00 PREC=0x00 TTL=114 ID=10267 DF PROTO=TCP SPT=443 DPT=53022 WINDOW=2050 RES=0x00 ACK PSH FIN URGP=0 
Dez 21 09:12:51 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:98:9b:cb:0d:b5:33:08:00 SRC=52.114.78.128 DST=192.168.10.90 LEN=121 TOS=0x00 PREC=0x00 TTL=113 ID=48705 DF PROTO=TCP SPT=443 DPT=53024 WINDOW=2051 RES=0x00 ACK PSH FIN URGP=0 
Dez 21 09:12:52 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:44:1c:a8:8a:bb:e3:08:00 SRC=192.168.10.127 DST=192.168.10.90 LEN=186 TOS=0x00 PREC=0x00 TTL=64 ID=40758 DF PROTO=TCP SPT=8009 DPT=35416 WINDOW=1425 RES=0x00 ACK PSH FIN URGP=0

journalctl -since="2 minutes ago"

Dez 29 20:37:19 manjaro systemd[1819]: Started Application launched by gsd-media-keys.
Dez 29 20:37:19 manjaro dbus-daemon[1844]: [session uid=1000 pid=1844] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.232' (uid=1000 pid=18834 comm="gnome-terminal ")
Dez 29 20:37:19 manjaro systemd[1819]: Starting GNOME Terminal Server...
Dez 29 20:37:19 manjaro dbus-daemon[1844]: [session uid=1000 pid=1844] Successfully activated service 'org.gnome.Terminal'
Dez 29 20:37:19 manjaro systemd[1819]: Started GNOME Terminal Server.
Dez 29 20:37:19 manjaro systemd[1819]: Started VTE child process 18860 launched by gnome-terminal-server process 18839.
Dez 29 20:37:23 manjaro gnome-shell[1917]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x558e05536320] is on because it needs an allocation.
Dez 29 20:37:23 manjaro gnome-shell[1917]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x558e068bbae0] is on because it needs an allocation.
Dez 29 20:37:23 manjaro gnome-shell[1917]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x558e0816dbc0] is on because it needs an allocation.
Dez 29 20:37:31 manjaro systemd-resolved[751]: Failed to send hostname reply: Transport endpoint is not connected
Dez 29 20:37:32 manjaro spotify.desktop[2203]: [2021/12/29 20:37:32:7243] ERR: getaddrinfo failed: -2
Dez 29 20:37:37 manjaro systemd[1819]: Started Application launched by gnome-shell.
Dez 29 20:37:38 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:37:38 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:37:39 manjaro firefox.desktop[17893]: Failed to establish dbus connection
Dez 29 20:37:39 manjaro firefox.desktop[2198]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Dez 29 20:37:43 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:01:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=56106 DF PROTO=2 
Dez 29 20:37:44 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:37:44 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:37:58 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Down
Dez 29 20:37:59 manjaro spotify.desktop[2203]: [2021/12/29 20:37:59:9748] ERR: getaddrinfo failed: -2
Dez 29 20:37:59 manjaro steam.desktop[3960]: LogonFailure No Connection
Dez 29 20:38:01 manjaro NetworkManager[1133]: <info>  [1640806681.3524] device (enp39s0): carrier: link connected
Dez 29 20:38:01 manjaro kernel: r8169 0000:27:00.0 enp39s0: Link is Up - 1Gbps/Full - flow control off
Dez 29 20:38:01 manjaro NetworkManager[1133]: <info>  [1640806681.3525] device (enp39s0): DHCPv4 lease renewal requested
Dez 29 20:38:01 manjaro NetworkManager[1133]: <info>  [1640806681.3896] dhcp4 (enp39s0): canceled DHCP transaction
Dez 29 20:38:01 manjaro NetworkManager[1133]: <info>  [1640806681.3896] dhcp4 (enp39s0): state changed bound -> terminated
Dez 29 20:38:01 manjaro NetworkManager[1133]: <info>  [1640806681.3899] dhcp4 (enp39s0): activation: beginning transaction (timeout in 45 seconds)
Dez 29 20:38:01 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=57858 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 29 20:38:01 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=57927 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 29 20:38:01 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:38:01 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:38:01 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC= SRC=192.168.10.90 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=255 ID=57958 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 29 20:38:02 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:00:00:fc:98:9b:cb:0d:b5:33:08:00 SRC=192.168.10.1 DST=224.0.0.252 LEN=62 TOS=0x00 PREC=0x00 TTL=1 ID=10918 PROTO=UDP SPT=5355 DPT=5355 LEN=42 
Dez 29 20:38:02 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:b0:e4:d5:c7:4e:3b:08:00 SRC=192.168.10.109 DST=192.168.10.90 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=21568 DF PROTO=UDP SPT=50388 DPT=55566 LEN=524 
Dez 29 20:38:02 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:44:1c:a8:8a:bb:e3:08:00 SRC=192.168.10.127 DST=192.168.10.90 LEN=306 TOS=0x00 PREC=0x00 TTL=64 ID=22536 DF PROTO=UDP SPT=55888 DPT=55566 LEN=286 
Dez 29 20:38:05 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=01:00:5e:7f:ff:fa:02:11:32:21:27:8c:08:00 SRC=192.168.10.11 DST=239.255.255.250 LEN=119 TOS=0x00 PREC=0x00 TTL=2 ID=65019 DF PROTO=UDP SPT=39301 DPT=1982 LEN=99 
Dez 29 20:38:08 manjaro dbus-daemon[1844]: [session uid=1000 pid=1844] Activating service name='org.gnome.gedit' requested by ':1.153' (uid=1000 pid=12842 comm="nemo ")
Dez 29 20:38:08 manjaro dbus-daemon[1844]: [session uid=1000 pid=1844] Successfully activated service 'org.gnome.gedit'
Dez 29 20:38:18 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:b0:2a:43:38:10:18:08:00 SRC=192.168.10.115 DST=192.168.10.90 LEN=398 TOS=0x00 PREC=0x00 TTL=64 ID=23501 DF PROTO=TCP SPT=8009 DPT=41992 WINDOW=294 RES=0x00 ACK PSH URGP=0 
Dez 29 20:38:19 manjaro NetworkManager[1133]: <info>  [1640806699.3632] dhcp4 (enp39s0): state changed unknown -> bound, address=192.168.10.90
Dez 29 20:38:19 manjaro dbus-daemon[1132]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1133 comm="/usr/bin/NetworkManager --no-daemon ")
Dez 29 20:38:19 manjaro kernel: audit: type=1130 audit(1640806699.371:361): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 29 20:38:19 manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 29 20:38:19 manjaro systemd[1]: Starting Network Manager Script Dispatcher Service...
Dez 29 20:38:19 manjaro dbus-daemon[1132]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 29 20:38:19 manjaro systemd[1]: Started Network Manager Script Dispatcher Service.
Dez 29 20:38:24 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:38:24 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:38:24 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:38:24 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:38:29 manjaro steam.desktop[3960]: LogonFailure No Connection
Dez 29 20:38:30 manjaro systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dez 29 20:38:30 manjaro audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 29 20:38:30 manjaro kernel: audit: type=1131 audit(1640806710.125:362): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dez 29 20:38:30 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:b0:e4:d5:c7:4e:3b:08:00 SRC=192.168.10.109 DST=192.168.10.90 LEN=355 TOS=0x00 PREC=0x00 TTL=64 ID=18917 DF PROTO=TCP SPT=8009 DPT=55376 WINDOW=361 RES=0x00 ACK PSH URGP=0 
Dez 29 20:38:37 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:98:9b:cb:0d:b5:33:08:00 SRC=142.250.179.206 DST=192.168.10.90 LEN=181 TOS=0x00 PREC=0x00 TTL=124 ID=27919 PROTO=TCP SPT=443 DPT=49740 WINDOW=267 RES=0x00 ACK PSH FIN URGP=0 
Dez 29 20:38:44 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff52 with keysym ff52 (keycode 6f).
Dez 29 20:38:44 manjaro gnome-shell[1917]: Window manager warning: Overwriting existing binding of keysym ff54 with keysym ff54 (keycode 74).
Dez 29 20:38:47 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:b0:2a:43:38:10:18:08:00 SRC=192.168.10.115 DST=192.168.10.90 LEN=398 TOS=0x00 PREC=0x00 TTL=64 ID=23507 DF PROTO=TCP SPT=8009 DPT=41992 WINDOW=294 RES=0x00 ACK PSH URGP=0 
Dez 29 20:38:51 manjaro kernel: [UFW BLOCK] IN=enp39s0 OUT= MAC=2c:f0:5d:25:b7:28:98:9b:cb:0d:b5:33:08:00 SRC=142.250.179.206 DST=192.168.10.90 LEN=181 TOS=0x00 PREC=0x00 TTL=124 ID=29705 PROTO=TCP SPT=443 DPT=49740 WINDOW=267 RES=0x00 ACK PSH FIN URGP=0 
Dez 29 20:38:52 manjaro systemd[1819]: Started Application launched by gsd-media-keys.
Dez 29 20:38:52 manjaro systemd[1819]: Started VTE child process 19154 launched by gnome-terminal-server process 18839.

And here is some system information:

inxi --admin --verbosity=7 --filter --no-host --width

System:
  Kernel: 5.16.2-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=4140d0fa-02f5-4b8c-bbf5-6abd7c894597 rw rootflags=subvol=@ quiet
    cryptdevice=UUID=6fcf6232-87f8-4c22-baba-3472efeab7e9:luks-6fcf6232-87f8-4c22-baba-3472efeab7e9
    root=/dev/mapper/luks-6fcf6232-87f8-4c22-baba-3472efeab7e9
    resume=/dev/mapper/luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 loglevel=3
    resume_offset=2368768 nowatchdog nvme_load=YES nvidia-drm.modeset=1
  Desktop: GNOME 41.3 tk: GTK 3.24.31 wm: gnome-shell dm: GDM 41.3
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: A.A0
    date: 06/22/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 31.33 GiB used: 3.99 GiB (12.7%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2503 high: 3628 min/max: 2200/4426 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2176 2: 3518
    3: 3600 4: 2063 5: 2200 6: 2196 7: 2200 8: 2199 9: 3253 10: 2131 11: 3628
    12: 2086 13: 2202 14: 2200 15: 2200 16: 2200 bogomips: 115251
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sev sev_es sha_ni skinit smap smca sme smep ssbd sse
    sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce
    topoext tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
    vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
    conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 495.46
    alternate: nouveau,nvidia_drm bus-ID: 2d:00.0 chip-ID: 10de:1b80
    class-ID: 0300
  Device-2: Sunplus Innovation FHD Camera Microphone type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-2.3:8 chip-ID: 1bcf:28c4
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org 1.21.1.3 compositor: gnome-shell driver:
    loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5560x1920 s-dpi: 96 s-size: 1471x508mm (57.9x20.0")
    s-diag: 1556mm (61.3")
  Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 96
    size: 510x290mm (20.1x11.4") diag: 587mm (23.1")
  Monitor-2: HDMI-0 res: 1080x1920 hz: 60
  Monitor-3: DP-4 res: 2560x1440 dpi: 109 size: 598x336mm (23.5x13.2")
    diag: 686mm (27")
  OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2 v: 4.6.0 NVIDIA 495.46
    direct render: Yes
Audio:
  Device-1: NVIDIA GP104 High Definition Audio driver: snd_hda_intel v: kernel
    bus-ID: 2d:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 2f:00.4 chip-ID: 1022:1487
    class-ID: 0403
  Device-3: JMTek LLC. USB PnP Audio Device type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2.1:5 chip-ID: 0c76:161f
    class-ID: 0300
  Device-4: Sunplus Innovation FHD Camera Microphone type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-2.3:8 chip-ID: 1bcf:28c4
    class-ID: 0102 serial: <filter>
  Device-5: Samson Meteorite condenser microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-5:6 chip-ID: 17a0:0120
    class-ID: 0300
  Sound Server-1: ALSA v: k5.16.2-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.43 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel port: f000 bus-ID: 27:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 28:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:4
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 maj-min: 254:0
    type: LUKS dm: dm-0 size: 1.82 TiB
  Components:
  p-1: nvme0n1p2 maj-min: 259:2 size: 1.82 TiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.27 TiB used: 271.37 GiB (11.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: PNY model: CS3030 2000GB SSD
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: CS303224 temp: 31.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Crucial model: CT500P1SSD8
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: P3CR021 temp: 42.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 271.37 GiB (14.6%)
    fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 720 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: FF05-AEF1
  ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 271.37 GiB (14.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
  ID-4: /swap raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 271.37 GiB (14.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
  ID-5: /var/cache raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 271.37 GiB (14.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
  ID-6: /var/cache/pacman/pkg raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 271.37 GiB (14.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
  ID-7: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 271.37 GiB (14.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-6fcf6232-87f8-4c22-baba-3472efeab7e9 label: N/A
    uuid: 4140d0fa-02f5-4b8c-bbf5-6abd7c894597
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 38 GiB used: 0 KiB (0.0%) priority: -2
    file: /swap/swapfile
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:4 size: 99 MiB fs: vfat label: N/A
    uuid: EC75-B0E0
  ID-2: /dev/nvme1n1p2 maj-min: 259:5 size: 465.66 GiB fs: bitlocker
    label: N/A uuid: N/A
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Texas Instruments TUSB8041 4-Port Hub ports: 4 rev: 2.1
    speed: 480 Mb/s chip-ID: 0451:8142 class-ID: 0900
  Hub-3: 1-2:3 info: Super Top 4-Port hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 14cd:8601 class-ID: 0900
  Device-1: 1-2.1:5 info: JMTek LLC. USB PnP Audio Device type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1
    speed: 12 Mb/s power: 100mA chip-ID: 0c76:161f class-ID: 0300
  Device-2: 1-2.2:7 info: Razer USA Mamba Elite (Wired) type: Mouse,Keyboard
    driver: razermouse,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 500mA
    chip-ID: 1532:006c class-ID: 0300
  Device-3: 1-2.3:8 info: Sunplus Innovation FHD Camera Microphone
    type: Video,Audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s power: 500mA chip-ID: 1bcf:28c4 class-ID: 0102
    serial: <filter>
  Device-4: 1-2.4:9 info: Razer USA BlackWidow X Chroma type: Keyboard,Mouse
    driver: razerkbd,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 500mA
    chip-ID: 1532:0216 class-ID: 0300
  Device-5: 1-4:4 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029
    class-ID: e001
  Device-6: 1-5:6 info: Samson Meteorite condenser microphone
    type: Audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 3
    rev: 1.1 speed: 12 Mb/s power: 56mA chip-ID: 17a0:0120 class-ID: 0300
  Hub-4: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-5: 2-1:2 info: Texas Instruments TUSB8041 4-Port Hub ports: 4 rev: 3.0
    speed: 5 Gb/s chip-ID: 0451:8140 class-ID: 0900
  Hub-6: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-5:2 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s
    power: 500mA chip-ID: 1462:7c35 class-ID: 0300 serial: <filter>
  Hub-7: 3-6:3 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0608 class-ID: 0900
  Hub-8: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-9: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 56 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 395 Uptime: 33m wakeups: 0 Init: systemd v: 250 tool: systemctl
  Compilers: gcc: 11.1.0 Packages: pacman: 1324 lib: 412 Shell: Zsh v: 5.8
  running-in: gnome-terminal inxi: 3.3.12

pacman -Qqs resolv

geoip
libmicrodns
openresolv
python-resolvelib

/etc/systemd/resolved.conf
Everything commented out.

lspci -vv (relevant bit)

27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 36
	IOMMU group: 23
	Region 0: I/O ports at f000 [size=256]
	Region 2: Memory at fc700000 (64-bit, non-prefetchable) [size=64K]
	Region 4: Memory at fc710000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

Two questions to start off:

How do I switch from r8169 to r8168? I tried yay r8168 and that also blacklists r8169, but when I reboot I don’t have any network connection. Also lspci -vv does not show r8168:
Kernel modules: r8169
How do I switch my resolver to something else than systemd-resolved (e.g. openresolv)? I tried lots I found on the internet but could not find anything working. I don’t really understand the Arch Wiki. I can install openresolv but it’s not clear to me how to get rid off systemd-resolved.

Please help me, I really don’t want to go back to Windows and this is getting super annoying

ricklinux · January 22, 2022, 4:14pm

Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169

I don’t think you can use the r8168 module. You have rtl8125 which is 2.5 GB network and it should run on the r8169 kernel module.

Is the EndeavourOS install nothing modified or changed? No firewall? Just fresh install? That’s how i would test it.

There is a UEFI Bios update in the works for that board but it is in beta still so i would wait until the final release and then update it.

rKJ9Db · January 22, 2022, 4:58pm

Right, that explains why r8168 doesn’t load at all.

I installed EndeavourOS using this guide. I installed some software like Firefox, Evolution, Steam etc. and the most “customization” would probably be GNOME Dash-to-Panel. I can’t really test it on a completely fresh install as it sometimes takes days of usage until the issue appears… And I need to use my computer in the meantime. Firewall is enabled, however on my old install disabling ufw didn’t make a difference.

Yeah I saw that but don’t think the board is the issue. I first installed Manjaro ~1 year ago and ran it for several months without issue. Then suddenly (maybe after an update?) the issue appeared. I never updated my UEFI in that time. In fact I was running a rather old version until a month ago, when I decided to upgrade to check if that mitigates the issue - it did not.

Do you maybe have any hints on commands I could run for better logs when the issue appears the next time? I feel a bit helpless just throwing random journalctl command at the problem… Some sort of verbose logging for the network stack of some sort?

Thanks for your reply.

ricklinux · January 22, 2022, 5:49pm

How old is your router equipment because you say it happens on all kernels? I would check that as well as cables. At minimum reset the router. Also cables are cheap best to get Cat6 if you replace any. I guess when it does disconnect maybe look at dmesg. Make sure the r8168 package is not installed. You could check but if you used the latest ISO it shouldn’t be but you may have installed it trying to switch? Does dmesg show anything currently? Post the link.

sudo dmesg | eos-sendlog

Edit: When the current UEFI Bios update is released i would definitely update it. It may not have any relevance to the current problem but they are really important for Ryzen processor platform.

rKJ9Db · January 22, 2022, 6:38pm

It’s the current flagship model of the largest manufacturer in my country - pretty many people use it and it’s still in active support.
I don’t believe its my networking as others computers in the house don’t have this issue (MacBook, Windows, Linux NAS with kernel 5.04). I have a rather new Cat6 cable running to my PC, directly from the router.
I also don’t think its the cable. A few weeks back the problems were so bad I had to switch to my Windows dual boot for 2+ weeks so I could get work done (I had like 5 disconnects per day throwing me out of work-related videocalls…). Problems were immediatly gone on Windows. Then I returned to Linux and it started again the same day. Could be a coincidence but over 2 weeks without a disconnect seems pretty promising to me

Thanks for the command. I will run it the next time this happens. I can also just sudo dmesg > log.txt right? Because upload won’t work without a network connection.

Here is a dmesg in working state: https://pastebin.com/0yBwHei2

Yes I had it installed manually and uninstalled it again after it didn’t work.

Cheers, will remember.

ricklinux · January 22, 2022, 6:53pm

Well i see it in a working state anyway. All you can do is monitor it and see with updates if it gets better.

[    6.229025] RTL8226 2.5Gbps PHY r8169-0-2700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2700:00, irq=MAC)
[    6.372504] r8169 0000:27:00.0 enp39s0: Link is Down
[    7.978475] usb 1-2.3: Warning! Unlikely big volume range (=3896), cval->res is probably wrong.
[    7.978480] usb 1-2.3: [7] FU [Mic Capture Volume] ch = 1, val = 200/4096/1
[    7.978629] usbcore: registered new interface driver snd-usb-audio
[    8.547055] IPv6: ADDRCONF(NETDEV_CHANGE): enp39s0: link becomes ready
[    8.547165] r8169 0000:27:00.0 enp39s0: Link is Up - 1Gbps/Full - flow control off

tbg · January 22, 2022, 8:43pm

Firstly, Windows has zero bearing on Linux. It is still possible that cabling is your problem. I have seen many times over where disconnects occur in Linux, but Windows is fine. When the cable is upgraded sometimes the problem goes away in Linux. I would suggest cat7 cabling because of the speed capabilities of your card.

I would also suggest you make sure your router’s firmware is up to date. If it is, then I would reset your router back to the factory default settings as this can sometimes cure connectivity issues. Sometimes only Linux is kicked off the network and Windows machines work fine with a specific router. If you have an alternate router available to you then swap in a different router temporarily as a test. Also, changing some settings such as those pertaining to QOS in the router may help. Also, if you are using cloudflare as your DNS server, switch to an alternate, because some router hardware doesn’t play well with it when using Linux.

As we don’t know if this is specifically an Ethernet issue, I would suggest disconnecting your network cable and then test your wifi connection’s reliability. If this still happens over wifi it is more likely to be a configuration issue, than something specific to your Ethernet.

You say you can not simply reconnect once your connection goes down, and that you need to reboot. Often simply doing an rmmod of your network driver and then reloading the driver via a modprobe command is enough to get the connection working without requiring a restart. In more stubborn cases stopping and restarting all network components is required to avoid having to reboot.

Please work through my suggestions methodically and post back all results to aid in finding a solution.

rKJ9Db · January 27, 2022, 12:14pm

Here a dmesg during a disconnect: https://pastebin.com/DNK1amiz

I upgraded the cable very recently as I moved homes. I decided to go with cat6 because none of my network equipment besides my computer supports more than Gigabit. I already had the issue with the old cable as well.

Router is up-to-date (has autoupdate). I tried resetting after your post, but no luck. I also disabled any QoS changes I had made. As DNS I am currently using Google. Switching to OpenDNS did not make a difference.

Good idea, I will try this next.

Thanks for the hint, this actually works! I can run sudo modprobe -r r8169 && sudo modprobe r8169 and the connection comes back. At least now I don’t have to crawl to the back of computer the next time this happens…

tbg · January 28, 2022, 3:08am

It sipped my mind the exact model you were using, then I had a recollection of another driver package for your adapter. If I’m not mistaken this driver may help (if you haven’t tested it before):

https://aur.archlinux.org/packages/r8125-dkms

If that driver doesn’t correct your dropped connection issue, and you can’t find a proper fix, I might have another alternative for you. I could post you a service I wrote that will automatically reconnect within a few seconds if your connection goes down. Not a fix of course, but it would make things far less inconvenient until your issue is resolved.

rKJ9Db · February 6, 2022, 10:36am

@tbg I tried the r8125 driver and the issue reappeared Then I temporarily tried another cable - same result. I am now on WLAN and will report back if it happens again.

Thank you for your offer for writing a service! If I can’t fix the issue and decide to stay on Linux, it would be greatly appreciated. However for now I think it’s good the issue shows itself clearly, so I know if my fixing attempts actually work.

rKJ9Db · March 1, 2022, 4:08pm

I’m back! Have been on WLAN the last few weeks and never had any issues. So we can probably rule out the config on the router side.

Back on LAN again since a few hours and had the first disconnect already

Not sure how to go from here. Any ideas?

Oh and @tbg I would highly appreciate if you could post that service for the modprobe command above that seems to work. Thank you in advance!

However I still need to get this fixed properly. For video calls a few seconds disconnect is probably fine, but not with online video games…

ricklinux · March 1, 2022, 4:29pm

Are you back using the kernel module rather than the installed AUR package. What program are you using on Linux for video call? Maybe it’s the application not the network.

rKJ9Db · March 1, 2022, 6:30pm

Yes, I’m back on the kernel module. I’m fairly sure it isn’t a foreground application problem because it happens pretty much anywhere:

MS Teams calls in the native app and in Chromium
While just browsing the web with Firefox
While playing different Steam and Lutris games
While working with LibreOffice

I do have a few backgrounds programs running such as Telegram, Spotify, Evolution, KeePassXC and Dropbox. I’ll stop them now, maybe they are triggering something. I’ll report back.

But if its an application, shouldn’t we see something in journalctl?

ricklinux · March 1, 2022, 7:17pm

Here it shows

[    6.229025] RTL8226 2.5Gbps PHY r8169-0-2700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2700:00, irq=MAC)

27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE

So on one it’s showing RTL8226 and the other is RTL8125
Have you tried it with the AUR package r8125-dkms but make sure the r8169 module is blacklisted.

tbg · March 2, 2022, 12:02pm

You can test this service I wrote a ways back.

Auto Restart Network Service

This service will hopefully alleviate the inconvenience of having to restart your computer by automatically restarting your network connection for you.

This service will ping Google’s servers to determine if your connection is working. If your connection is down, then the script will automatically initiate a restart of your network connection. This will hopefully revive your connection without the need for manual intervention. Sometimes a recurring ping as used in this service may also help to keep a flaky connection alive.

This service should automatically restart your network connection shortly after it drops. From the time when it detects a loss of connectivity the script can be as quick as 4 seconds in re-initiating a connection. The script performs an automatic restart of your network connection to avoid a reboot or any other manual intervention.

For this functionality you must create one service file and one script.

Network Restart Service:

Create the service file:

/etc/systemd/system/network-restart.service

With the following contents:

#cat /etc/systemd/system/network-restart.service
#/etc/systemd/system/network-restart.service
#systemctl enable network-restart.service
#systemctl start network-restart.service
#systemctl stop network-restart.service
#systemctl disable network-restart.service
#systemctl status network-restart.service
#systemctl daemon-reload

[Unit]
Description=Network Restart Service 
WantedBy=network-pre.target 

[Service]
User=root
Type=simple
Restart=always
RestartSec=3
Restart=on-failure
StartLimitIntervalSec=0
ExecStartPre=-sleep 10
ExecStart=/usr/local/sbin/network_restart.sh

[Install]
WantedBy=network.target

Once you have created and saved the service file, enable the service:

systemctl enable network-restart.service

Network Restart Script:

With a text editor create:

/usr/local/sbin/network_restart.sh

Script contents:

#!/bin/bash
#cat /usr/local/sbin/network_restart.sh
echo "to exit script press CTRL+C"
  sleep 2
trap "killall -9 network_restart; sleep 2; exit" INT
while true; do
     ping -c 1 8.8.8.8  | grep received
     if [ $? -eq 0 ]; then sleep 2
else
 notify-send 'Connection broken, restarting network connection'
    nmcli networking off
      systemctl stop NetworkManager
        #ip link set enp39s0 down
         modprobe -r r8169
         sleep 1
         modprobe r8169
         sleep .5
         #ip link set enp39s0 up
         #sleep .5
         systemctl start NetworkManager
        nmcli networking on
      sleep 10
     break
   fi
 done
exec bash "$0" "$@"

Make the script executable:

sudo chmod +x /usr/local/sbin/network_restart.sh

The group of numbers “8.8.8.8” is Googles server address. If you would prefer to ping another server such as Cloudflare then change the address to “1.1.1.1” instead.

There are several lines in the script that will need to be modified if you have different networking components. You can find the required information by running the command “inxi -n”. You must replace “enp39s0” with your adapters designation returned from the “inxi -n” command if you need to raise and lower your adapter. I currently have those steps disabled by comments in this version. You can enable those operations by simply removing those comments from the script.

As below:

ip link set enp39s0 down

ip link set enp39s0 up

You must also insert your driver module in place of “r8169” in the script if your adapter uses a different module. Modify these lines (as below) in the script to reflect the driver module your adapter uses:

modprobe -r r8169

modprobe r8169

After creating the service file and the associated script reboot the computer.

After rebooting you can use the following command to test how well the connection is reestablished after it is broken:

nmcli networking off

If you need to stop the script for any reason you can use this command:

killall -9 network_restart

I hope this helps some people with flakey adapters that drop the connection on a regular basis. While this is only a workaround hopefully it will make your adapter more usable until a permanent fix is found.

rKJ9Db · March 18, 2022, 6:04pm

@ricklinux Yeah sorry for the confusion, those logs were from different occasions. I reconfirmed and r8169 was definitely blacklisted.

@tbg Thank you very much for your effort! I haven’t tested it because I think I found a correlation!

I noticed the issue appears much more frequently when copying files around on my NAS! I have a Synology DS720+ (DSM 7.0.1-42218 Update 3 // Linux 4.4 // BTRFS) and when moving files around I often get the disconnect after a few GBs. It doesn’t always happen and when it does, it’s just randomly somewhere in the transfer (like after 3 of 7GB).

I can’t confirm the issue on Windows because Windows seems to have a “better” Samba implementation. When moving files around on the NAS it somehow tells the NAS to move the files on its own and the process is done instantly. On Linux however the actual bytes are rewritten which can take ages. Moving 100GB e.g. takes an hour on Linux and a few seconds in Windows… Side note: if you have a fix for this behaviour that would be appreciated!

Anyway, I at first thought it might be transferring large files somehow fails the connection, but e.g. when downloading a 100GB game from Steam there are no issues.

So maybe its really Samba related? Or maybe just “uploading” large amounts of data… But it’s not solely transferring files via Samba. Still happens randomly while browsing the web for example. But maybe there is still something off with the NAS? I host a lot of applications on there in Docker (Gitea, AdGuard, Mealie, PhotoPrism etc.) which I do frequently access.

My shares don’t auto-mount, I just have a bookmark in Nemo (my file browser) which mounts them on demand. I’ll check the next time it happens if shares are mounted.

Any input is appreciated! I’ll post logs as soon I have them. I tried gathering a journalctl of Samba, but now that I’m making this post it isn’t happening (ofc). Are there any other logs I can provide when this happens next? Samba maybe?

tbg · March 19, 2022, 2:30pm

Try using NFS, samba sucks.

https://wiki.archlinux.org/title/NFS

rKJ9Db · March 23, 2022, 11:02am

@tbg I looked into NFS, but it seems it does not support authentication. Is that true? I can only limit access by IP address but because my NAS is connected to a WireGuard network, anyone in the WireGuard network could change their IP address to mine and then receive access to my personal files. Synology seems to have an option for extra Kerberos auth but I don’t want to set that up.