You are not logged in.
Pages: 1
A few times a day my internet connection will drop. Normally only lasts a couple of minutes before reconnecting. I am using a TP LINK; all 3 lights on it remain a solid green when my connection drops. All other devices in my work fine. Any ideas guys?
journalctl logs = http://0x0.st/Hx7P.txt
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service | system
default.target | system
getty@tty1.service | getty.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
nvidia-persistenced.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
piavpn.service | multi-user.target.wants
pipewire.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
snapd.socket | sockets.target.wants
sshd.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
var-lib-snapd-snap-bare-5.mount | multi-user.target.wants
var-lib-snapd-snap-core18-2409.mount | multi-user.target.wants
var-lib-snapd-snap-core18-2714.mount | multi-user.target.wants
var-lib-snapd-snap-core20-1434.mount | multi-user.target.wants
var-lib-snapd-snap-core20-1828.mount | multi-user.target.wants
var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-161.mount | multi-user.target.wants
var-lib-snapd-snap-gnome\x2d3\x2d38\x2d2004-119.mount | multi-user.target.wants
var-lib-snapd-snap-gnome\x2d3\x2d38\x2d2004-99.mount | multi-user.target.wants
var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1534.mount | multi-user.target.wants
var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount | multi-user.target.wants
var-lib-snapd-snap-snapd-15904.mount | multi-user.target.wants
var-lib-snapd-snap-snapd-18357.mount | multi-user.target.wants
var-lib-snapd-snap-snap\x2dstore-558.mount | multi-user.target.wants
xdg-user-dirs-update.service | default.target.wantsLast edited by IsItWashable (2023-12-05 18:59:04)
Offline
Dec 05 18:35:51 archbtw NetworkManager[589]: <info> [1701801351.1316] manager: NetworkManager state is now CONNECTING
Dec 05 18:35:51 archbtw NetworkManager[589]: <info> [1701801351.1317] device (enp34s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 05 18:35:51 archbtw NetworkManager[589]: <info> [1701801351.1320] device (enp34s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 05 18:35:51 archbtw NetworkManager[589]: <info> [1701801351.1322] dhcp4 (enp34s0): activation: beginning transaction (timeout in 45 seconds)
Dec 05 18:35:52 archbtw NetworkManager[589]: <info> [1701801352.7150] dhcp6 (enp34s0): activation: beginning transaction (timeout in 45 seconds)
Dec 05 18:35:52 archbtw NetworkManager[589]: <info> [1701801352.7153] policy: set 'Wired connection 1' (enp34s0) as default for IPv6 routing and DNS
Dec 05 18:35:52 archbtw NetworkManager[589]: <info> [1701801352.7923] dhcp6 (enp34s0): state changed new lease
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1798] dhcp4 (enp34s0): state changed new lease, address=192.168.0.13
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1800] policy: set 'Wired connection 1' (enp34s0) as default for IPv4 routing and DNS
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1916] device (enp34s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1936] device (enp34s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1938] device (enp34s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1941] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1943] device (enp34s0): Activation: successful, device activated.
Dec 05 18:35:53 archbtw NetworkManager[589]: <info> [1701801353.1987] manager: NetworkManager state is now CONNECTED_SITE1. What's you exact metric for that
2. Can you still "ping _gateway" at that point?
3. The VPN is probably the obvious contender, do you experience the drops w/o it?
Offline
Bumping this thread about a year later as this problem has come back. It happens even when my VPN is disconnected.
systemctl list-units --type service --no-pager
UNIT LOAD ACTIVE SUB DESCRIPTION
dbus-broker.service loaded active running D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
kmod-static-nodes.service loaded active exited Create List of Static Device Nodes
ldconfig.service loaded active exited Rebuild Dynamic Linker Cache
lvm2-monitor.service loaded active exited Monitoring of LVM2 mirrors, snapshots…
NetworkManager.service loaded active running Network Manager
nvidia-persistenced.service loaded active running NVIDIA Persistence Daemon
piavpn.service loaded active running Private Internet Access daemon
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
sshd.service loaded active running OpenSSH Daemon
systemd-fsck@dev-disk-by\x2duuid-3157… loaded active exited File System Check on /dev/disk/by-uui…
systemd-journal-catalog-update.service loaded active exited Rebuild Journal Catalog
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save OS Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-tmpfiles-setup-dev-early.serv… loaded active exited Create Static Device Nodes in /dev gr…
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create System Files and Directories
systemd-udev-load-credentials.service loaded active exited Load udev Rules from Credentials
systemd-udev-trigger.service loaded active exited Coldplug All udev Devices
systemd-udevd.service loaded active running Rule-based Manager for Device Events …
systemd-update-done.service loaded active exited Update is Completed
systemd-update-utmp.service loaded active exited Record System Boot/Shutdown in UTMP
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Virtual Console Setup
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
user-runtime-dir@1000.service loaded active exited User Runtime Directory /run/user/1000
user@1000.service loaded active running User Manager for UID 1000
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
36 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.Last edited by IsItWashable (2024-07-05 17:57:14)
Offline
1. What's you exact metric for that
2. Can you still "ping _gateway" at that point?
There was no indication of a network loss in your previous journal.
Offline
I have just noticed a trend. This only happens when I have discord open. Anyway to troubleshoot this?
Offline
Here is an updated log https://0x0.st/XBQn.txt
My connection dropped at around 16:25, VPN was connected and discord was not open.
Offline
r8169aren't there some issues with this family of realtek chips currently, are there?
Offline
Jul 06 16:25:06 archbtw NetworkManager[547]: <info> [1720279506.5551] caught SIGTERM, shutting down normally.
Jul 06 16:25:06 archbtw systemd[1]: Stopping Network Manager...
…
Jul 06 16:25:06 archbtw systemd[1]: Stopped Network Manager.
Jul 06 16:25:06 archbtw systemd[1]: Starting Network Manager...You restarted NM, why?
Afterwards you're getting a LAN, but not a WAN connection on subsequent tries:
Jul 06 16:25:06 archbtw NetworkManager[763699]: <info> [1720279506.7732] dhcp4 (enp34s0): state changed new lease, address=192.168.0.50
Jul 06 16:25:06 archbtw NetworkManager[763699]: <info> [1720279506.7861] manager: NetworkManager state is now CONNECTED_SITE
Jul 06 16:25:06 archbtw NetworkManager[763699]: <info> [1720279506.9065] dhcp6 (enp34s0): state changed new lease
…
Jul 06 16:28:32 archbtw NetworkManager[824188]: <info> [1720279712.6897] dhcp4 (enp34s0): state changed new lease, address=192.168.0.50
Jul 06 16:28:32 archbtw NetworkManager[824188]: <debug> [1720279712.6984] dhcp4 (enp34s0): accept lease
Jul 06 16:28:32 archbtw NetworkManager[824188]: <info> [1720279712.7026] manager: NetworkManager state is now CONNECTED_SITEThis smells like it's actually an issue w/ your ISP
1. What's you exact metric for that
2. Can you still "ping _gateway" at that point?
@cryptearth there was a race condition in setting up the driver but that would kill network completely and stall the boot - and is fixed in 6.9.7
Last edited by seth (2024-07-06 19:10:30)
Offline
I can't remember why or if I did even restart Network Manger. I may have just turned my TP-LINK off and on.
What type of issue could it be with my ISP? I don't have these issues with any other devices in my house.
I will try "ping _gateway" next time this occurs and get back to you. Also I don't know what you mean by "metric"
Last edited by IsItWashable (2024-07-06 19:31:44)
Offline
Edit: "what *exactly* makes you think your network doesn't work"
"metric" == "way to measure things"
Last edited by seth (2024-07-06 19:33:09)
Offline
Web pages won't load, VPN disconnects. I tried pinging google in the terminal and get the error "temporary failure in name resolution"
Offline
When this happens again, check
ping -c3 _gateway
ping -c3 8.8.8.8
ping -c3 google.comit might be just a DNS issue (in which case you could ping 8.8.8.8 but not google.com) - NM defaults to asking ping.archlinux.org to see whether the internet works and move to CONNECTED_GLOBAL, https://wiki.archlinux.org/title/Networ … nnectivity
Offline
~ ❯ ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2021ms
~ ❯ ping -c3 _gateway
PING _gateway (fe80::3e89:94ff:fec1:e4a9%enp34s0) 56 data bytes
From archbtw (fe80::3862:47c1:7e56:6fbf%enp34s0) icmp_seq=1 Destination unreachable: Address unreachable
From archbtw (fe80::3862:47c1:7e56:6fbf%enp34s0) icmp_seq=2 Destination unreachable: Address unreachable
From archbtw (fe80::3862:47c1:7e56:6fbf%enp34s0) icmp_seq=3 Destination unreachable: Address unreachable
--- _gateway ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2030ms
~ ❯ ping -c3 google.com
ping: google.com: Temporary failure in name resolutionLast edited by IsItWashable (2024-07-07 15:08:09)
Offline
Why's your _qateway a link local IPv6 at this point?
Did you try to combat the situation and stop/restart NM or something like that?
Don't - and if it happens again try to just "ping -c3 192.168.0.1"
Revisiting your journal
Jul 06 16:21:17 archbtw NetworkManager[547]: <info> [1720279277.2180] manager: (wgpia0): new WireGuard device (/org/freedesktop/NetworkManager/Devices/4) is the only thing that happens network-wise before your restarted NM (what's likely marking the preceived failure)
What's the idea here?
Do you have https://wiki.archlinux.org/title/WireGu … ally_reset ?
Offline
The VPN has the option to use either OpenVPN or Wireguard. Under both protocols the disconnects happen.
I can change it back to OpenVPN and get back to you if it disconnects again.
I may have restarted NetworkManager, I cannot remember.
Either way it has just happened again now so i will post a fresh log - http://0x0.st/XBGq.txt
Last edited by IsItWashable (2024-07-08 13:15:28)
Offline
and if it happens again try to just "ping -c3 192.168.0.1"
Also "ip a; ip r", but
Jul 08 13:15:03 archbtw NetworkManager[573]: <info> [1720440903.3791] manager: NetworkManager state is now CONNECTED_GLOBALchanged to
Jul 08 13:25:29 archbtw NetworkManager[573]: <info> [1720441529.2005] manager: NetworkManager state is now CONNECTED_SITEafter
Jul 08 13:23:35 archbtw NetworkManager[573]: <debug> [1720441415.6066] platform: (wgpia0) signal: link added: 3: wgpia0 <NOARP,DOWN;pointopoint,noarp> mtu 1420 arp 65534 wireguard* not-init addrgenmode eui64 driver wireguard tx-queue-len 1000 gso-max-size 65536 gso-max-segs 65535 gro-max-size 65536 rx:0,0 tx:0,0I'm pretty sure it's your VPN - reproduce the issue w/o that and then start to elaborate on the VPN provider/setup/… because there's not much beyond the wireguard entries in the journal.
Offline
Pages: 1