Connection drops with "Using degraded feature set TCP instead of UDP"

rKJ9Db · 14 December 2021 13:59

Hello,

since a few weeks I am experiencing a strange problem were a few times a day my Manjaro GNOME will randomly lose network connection. When this happens, I cannot even ping my router anymore.

The only thing fixing this is physically replugging the network cable or restarting the machine.

journalctl says:

-- 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.

I am pretty sure the lines with Using degraded feature set UDP instead of TCP for DNS server 9.9.9.9 are the explanation. Those lines appear every time the connection drops. I have tried googling the message and tried some fixes like changing DNS, disabling IPv6, disabling DNSSEC. No luck.

I get the same error when using my routers DNS or 1.1.1.1.

There is an open issue with systemd here: DNS fails with "Using degraded feature set" in logs until resolved is restarted · Issue #13432 · systemd/systemd · GitHub
However the workaround presented here ( systemctl restart systemd-resolved) does not work for me.

This is super annoying, especially with the connection dropping during important work calls.

My system is up-to-date and I am running 5.10 LTS.

What else can I try? What more relevant information can I provide?

Thanks!

mithrial · 14 December 2021 15:08

You have configured 9.9.9.9 as your PC’s DNS and probably set a wrong value about DNSoverTLS. What is your systemd-resolved settings?

It doesn’t matter what your router uses when you set a different on locally.

rKJ9Db · 14 December 2021 16:15

You mean my /etc/systemd/resolved.conf? Everything commented out.

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
#DNS=
#FallbackDNS=1.1.1.1#cloudflare-dns.com 9.9.9.10#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::10#dns.quad9.net 2001:4860:4860::8888#dns.google
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=yes
#LLMNR=yes
#Cache=yes
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

I also tried uncommenting DNSSEC=no, but no luck. I don’t have any additional files under /etc/systemd/resolved.conf.d/.

My GNOME NetworkManager looks like this (IPv6 is disabled):

9.9.9.9 is only my last DNS server, so I’m guessing it already failed on 192.168.10.10 (my local AdGuard Home) and 1.1.1.1.

rKJ9Db · 21 December 2021 09:31

Push please Happened again today Can I provide any more information?

Hanzel · 21 December 2021 10:29

Don’t bump your own thread, it is against the forum rules

If this is the case this might be a driver / hardware issue. As the restart of the service does not work either and your next hop is not there anymore.

This could be a symptom to, since your whole connection seems to drop.

Some questions that could help get some idea if your issue:
Do you dual boot with windows and have fastboot turned off?
Do you have errors in your log that could point to something about the network card?

Please provide some background info about your system and / or network card:
eg: $ journalctl -g enp5s0 where enp5s0 is your network card (this could be something else on your machine) &
$ inxi --admin --verbosity=7 --filter --no-host --width
See link below how to provide this info so it is reusable and searchable (no screenshots)

cscs · 21 December 2021 11:20

Also

pacman -Qqs resolv

linux-aarhus · 21 December 2021 12:04

Network issues are not easily troubleshooted. It often requires the user to understand network topology and being able to use some basic utilities to test and gather info on the infrastructure.

[root tip] Basic network know-how

Sometimes the resolver is at fault and switching your resolver from openresolv to systemd-resolved sometimes mitigates the issue.

Network errors can also occur if your kernel and modules has been updated and the system has not been restarted to load the new configuration.

rKJ9Db · 21 December 2021 12:07

Thank you for your replies @Hanzel and @cscs

These issues started only a few weeks ago and I didn’t have the issue before on 5.10 LTS. So I don’t think its a driver issue. A hardware defect is maybe possible, but again this only started recently and I don’t think its very likely to become defect in this very specific way. Sure, of course possible - but I believe its more a software issue.

I indeed dual boot with Windows, but haven’t in the last weeks since the issue appeared. Fastboot is turned off.

I had a closer look for hardware errors via journalctl -b -p err and sudo dmesg --level emerg,alert,crit,err,warn but could not find anything unusual here.

This is my journalctl -g enp39s0. This looks quite promising with all those errors, however I could not find any details on Google about the error. The IP address 52.112.218.x:3480 at the end belongs to Microsoft Azure DNS and the port is used by Microsoft Teams, which I was using during the disconnect. The disconnect however is not limited to the usage of Teams, it also happens while browsing other websites. Does someone know what this error message means?

-- 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

I removed most [UFW BLOCK] lines to make it more readable, I checked though if the IP address throwing the error was blocked - it was not. So I don’t think its a UFW problem. I also disabled my AdGuard Home DNS for testing, no luck.

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

This is my pacman -Qqs resolv:

libmicrodns
python-resolvelib
systemd-resolvconf

And my inxi:

System:
  Kernel: 5.10.84-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.10-x86_64
    root=UUID=98aebf4f-f565-4587-a4c7-eb15e3e9a9ae rw rootflags=subvol=@ quiet
    cryptdevice=UUID=ab08da97-7fdd-4a1a-b1bf-69d8c309bef6:luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6
    root=/dev/mapper/luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 splash
    apparmor=1 security=apparmor udev.log_priority=3
    resume=UUID=54e7458c-1785-43f4-8a32-ef4c32cca4c6
  Desktop: GNOME 41.2 tk: GTK 3.24.30 wm: gnome-shell dm: GDM 41.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0
    serial: <superuser required> UEFI: American Megatrends v: A.70
    date: 10/29/2020
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 31.34 GiB used: 7.63 GiB (24.3%)
  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: 2694 high: 4254
    min/max: 2200/5224:4957:5091:4690:4426:4823:4560 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 4067 2: 2109 3: 2137
    4: 2125 5: 2083 6: 4006 7: 2119 8: 2460 9: 3443 10: 2102 11: 2080 12: 2070
    13: 2098 14: 3819 15: 2135 16: 4254 bogomips: 115233
  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 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_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 and seccomp
  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.44
    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: 5-1.1:8 chip-ID: 1bcf:28c4
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org 1.21.1.2 compositor: gnome-shell driver:
    loaded: nvidia 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.44
    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: Samson Meteorite condenser microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-5:4 chip-ID: 17a0:0120
    class-ID: 0300
  Device-4: Sunplus Innovation FHD Camera Microphone type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-1.1:8 chip-ID: 1bcf:28c4
    class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.10.84-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.40 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>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 28:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
    chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 maj-min: 254:0
    type: LUKS dm: dm-0 size: 1.78 TiB
  Components:
  p-1: nvme0n1p7 maj-min: 259:3 size: 1.78 TiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.27 TiB used: 592.44 GiB (25.4%)
  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: 34.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 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: 44.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 1.78 TiB size: 1.78 TiB (100.00%) used: 592.44 GiB (32.5%)
    fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 label: N/A
    uuid: 98aebf4f-f565-4587-a4c7-eb15e3e9a9ae
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 732 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p6 maj-min: 259:2
    label: NO_LABEL uuid: DB78-5D22
  ID-3: /home raw-size: 1.78 TiB size: 1.78 TiB (100.00%)
    used: 592.44 GiB (32.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 label: N/A
    uuid: 98aebf4f-f565-4587-a4c7-eb15e3e9a9ae
  ID-4: /run/timeshift/backup raw-size: 1.78 TiB size: 1.78 TiB (100.00%)
    used: 592.44 GiB (32.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 label: N/A
    uuid: 98aebf4f-f565-4587-a4c7-eb15e3e9a9ae
  ID-5: /var/cache raw-size: 1.78 TiB size: 1.78 TiB (100.00%)
    used: 592.44 GiB (32.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 label: N/A
    uuid: 98aebf4f-f565-4587-a4c7-eb15e3e9a9ae
  ID-6: /var/log raw-size: 1.78 TiB size: 1.78 TiB (100.00%)
    used: 592.44 GiB (32.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ab08da97-7fdd-4a1a-b1bf-69d8c309bef6 label: N/A
    uuid: 98aebf4f-f565-4587-a4c7-eb15e3e9a9ae
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 38 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p5 maj-min: 259:1 label: N/A
    uuid: 54e7458c-1785-43f4-8a32-ef4c32cca4c6
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:5 size: 99 MiB fs: vfat label: N/A
    uuid: EC75-B0E0
  ID-2: /dev/nvme1n1p2 maj-min: 259:6 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
  Device-1: 1-4:3 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-2: 1-5:4 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-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-4: 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-5: 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-6: 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
  Device-1: 3-6.2:4 info: Shenzhen Goodix Goodix Fingerprint Device
    type: Abstract (modem),CDC-Data driver: cdc_acm interfaces: 2 rev: 2.0
    speed: 12 Mb/s power: 100mA chip-ID: 27c6:5042 class-ID: 0a00
    serial: <filter>
  Hub-7: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-8: 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-9: 5-1:7 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 1a40:0101 class-ID: 0900
  Device-1: 5-1.1: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-2: 5-1.2:9 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: 5-1.3:10 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
  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: 60.6 C mobo: N/A gpu: nvidia temp: 57 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 451 Uptime: 3h 54m wakeups: 0 Init: systemd v: 249
  tool: systemctl Compilers: gcc: 11.1.0 clang: 13.0.0 Packages: 1673
  pacman: 1667 lib: 501 flatpak: 0 snap: 6 Shell: Zsh v: 5.8
  running-in: gnome-terminal inxi: 3.3.10

Edit: @linux-aarhus Thank you. I will save your link for offline use and run a few of the tests the next time the connection drops. It seems I have installed systemd-resolvconf, do you think it makes sense to switch to openresolv for testing?
I don’t think its a kernel / modules update problem, the error today for example occured a few minutes after a fresh boot and I did not update or install anything on this boot.

Hanzel · 21 December 2021 13:57

Strange problem, I do not see a clear path to a solution, these are the worst kind of problems, it sometimes fails

Some actions I would try are:

This part has been known to have issues, sometimes needing to switch to another version, iirc one blacklists the r8169 so the previous one is used.

If you have ufw installed, does disabling it help in any way?

Are you sure the adguard solution you use is not interfering with anything, does removing 192.168.10.10 have a effect?

Another type of resolver could be an option.

straycat · 21 December 2021 14:57

I don’t know if it makes a difference but in your screen of network manager you have
192.168.10.10, 1.1.1.1, 9.9.9.9 and there should be no space between the commas like this
192.168.10.10,1.1.1.1,9.9.9.9

mithrial · 21 December 2021 15:59

Why do you even set Quad9 as your DNS provider when you want to use DNS filtering?

I don’t know if it’s actually using FIFO for the nameservers or a kind of round-robin, so you try with either only your Adguard or only Quad9.

rKJ9Db · 23 December 2021 10:59

It happend again. Different scenario this time however. For the first time, network was immediatly gone on boot. I kept getting these popups and the network connection in NetworkManager eventually disabled itself:
failed
Also no Using degraded feature set TCP instead of UDP for DNS server this time. But besides that it’s the same issue and it could be only resolved by replugging the network cable.

I ran a few commands from @linux-aarhus link (I skipped traceroute etc. as I didn’t even get a ping through):

nmcli device show | grep IP4 shows its in the wrong subnet (192.168.122.0/24 instead of 192.168.10.0/24):

IP4.ADDRESS[1]:                         192.168.122.1/24
IP4.GATEWAY:                            --
IP4.ROUTE[1]:                           dst = 192.168.122.0/24, nh = 0.0.0.0, mt = 0
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --

I can’t ping my router or local DNS:

> ping 192.168.10.1
ping: connect: Network is unreachable
> ping 192.168.10.10
ping: connect: Network is unreachable

systemctl status systemd-resolved says:

systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2021-12-23 09:52:00 CET; 14min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 737 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 38405)
     Memory: 3.4M
        CPU: 630ms
     CGroup: /system.slice/systemd-resolved.service
             └─737 /usr/lib/systemd/systemd-resolved

Dez 23 09:52:00 manjaro systemd[1]: Starting Network Name Resolution...
Dez 23 09:52:00 manjaro systemd-resolved[737]: Positive Trust Anchors:
Dez 23 09:52:00 manjaro systemd-resolved[737]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Dez 23 09:52:00 manjaro systemd-resolved[737]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-add>
Dez 23 09:52:00 manjaro systemd-resolved[737]: Using system hostname 'manjaro'.
Dez 23 09:52:00 manjaro systemd[1]: Started Network Name Resolution.
Dez 23 09:52:00 manjaro systemd-resolved[737]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.

And here’s my journalctl. The network failing is in the last ~60 lines:

Good hint. For now I tried upgrading to kernel 5.15 and updating my BIOS. Maybe that fixes it already. Otherwise I’ll check out r8168, which is directly supplied by Realtek (r8169 on the other hand is shipped in the kernel). However according to Realteks website they only supply drivers for up to kernel 5.6: Realtek PCIe FE / GBE / 2.5G / Gaming Ethernet Family Controller Software - REALTEK

Yes it was installed, however I deactivated it after your last post and the problem still occured. So turning it back on for now.

I had AdGuard Home blocking disabled for a few days, during which the error occured multiple times. However I now have removed 192.168.10.10 completely from my DNS list and replaced it with 1.1.1.1 only (to also address what @straycat mentioned).

Good question, never thought about the logic. I just assumed it would be FIFO, but sure now that you mention it… I just had them set as fallback servers so that when I update AdGuard Home, restart Docker or the server itself I can still use the internet on my computer. Happend a few times and I was annoyed, so I added them. But yeah I’ll keep that in mind now.

TL;DR: The next time the system fails I will try r8168 and another resolver. If anyone has more ideas until then, please keep them going! Cheers

Hanzel · 23 December 2021 13:24

From the journal it seems the network card is unable to find a dhcp server:

manjaro NetworkManager[760]: <warn>  [1640249596.1451] dhcp4 (enp39s0): request timed out

It tries 3 times and it times out. So either the packets do not reach the server or the server is not responding in time. So something is wonky there.

You have libvirt running and 192.168.122.0/24 is the default intern network it uses via a bridge: virbr0 the route set up to this network is normal since it would otherwise not be able to connect virtuals to the local network.

linux-aarhus · 24 December 2021 06:28

You seem to have a rogue dhcp service on your network.

The AdGuard service is causing your drops - I suggest you clean up your network - revert anything interfering - AdGuard - Pihole - what-ever services you have put in - either in form of services of physical devices.

Then start fresh.

Hanzel · 24 December 2021 13:59

Since rKJ9Db has only shared the lines beginning with IP4, this could come from any IP4 connection, eg: the virtual bridge libvirt uses has by default this same subnet by default:

GENERAL.DEVICE:                         virbr0
GENERAL.TYPE:                           bridge
GENERAL.HWADDR:                         52:54:00:9A:29:04
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected (externally))
GENERAL.CONNECTION:                     virbr0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADDRESS[1]:                         192.168.122.1/24
IP4.GATEWAY:                            --
IP4.ROUTE[1]:                           dst = 192.168.122.0/24, nh = 0.0.0.0, mt = 0
IP6.GATEWAY:                            --

linux-aarhus · 24 December 2021 14:04

Yes - could be - but ideas, conclusions and suggestions can only be based on provided info.

The provided info and the comment supplied indicates a rogue dhcp server - based on the provided info.

andreas85 · 24 December 2021 15:04

Maybe test another port on your router.

Once we had repeated network problems with one device. What have we not been looking for.

In reality, it was the connector on the network cable. The latch was no longer OK and the cable was not making secure contact. After exchanging the cable, the problems were gone.

rKJ9Db · 30 December 2021 09:44

So kernel 5.15 and the BIOS update did not help. I did not yet have time to check out how to change to the r8168 driver and how to switch resolver. I’ll do that next week.

Thats a good hint, I now set my IP manually in Network Manager. I had a static IP set for my computer anyway on the router (DHCP server), so I just set it to the same IP locally now too. Let’s see in the next days if a non-reachable DCHP was the problem.

I don’t think the DHCP server itself is the problem, no other devices on the network have any issues and a few weeks back it also worked on Manjaro.

I checked the 192.168.122.0/24 range at it indeed is my libvirt:

vmm

I disabled AdGuard for testing and issue appeared again a few hours later Not sure what else I can clean up besides resetting the whole router…

Can I scan my network for rogue DHCP servers? I’m 99% sure there isn’t one but I would like to be sure.

What port do you mean?

I really hope its not that, my cable is 20m and goes through several walls. Would be a huge pain to swap it. I’m fairly sure however its not issue, I’ve been using Windows the last few days (because I needed to get some work done without frequent disconnects) and the connection didn’t drop once. Could be a coincidence, but with Manjaro the issue appears 2-3 times a day and on Windows not once in the last week.

Here is another journalctl (before setting a static IP instead of DHCP). They look different every time…

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.

I’ll update next week when I’m back on Manjaro and have more time to troubleshoot. Thanks to all of you so far!

Hanzel · 30 December 2021 11:02

The link going down is the issue to solve.

One more thing that might interfere: fastboot in windows.

rKJ9Db · 2 January 2022 18:59

I’m afraid thats just me pulling the ethernet cable out 3 seconds later I get Link is Up, which is the plugging back in. It must therefore be something before the Link is Down. I included too much text after the actual disconnect, that was confusing. My bad!

I don’t even have a hyberfil.sys in Windows (too save space on my secondary, smaller Windows SSD) and that means Fast Boot cannot be enabled. I re-confirmed just now and it’s still off and greyed out.