You are not logged in.

Pages: 1

#1 2023-05-08 09:14:07

hawkis
Member
Registered: 2023-01-04
Posts: 13

Intermittent internet connection on specific network

I'm experiencing intermittent connectivity on my home network, both on WiFi and Ethernet. The internet works for about 10 seconds, then stops for a few minutes, before temporarily working again, and then it stops. The issue began after switching between Ethernet and WiFi. My system has a dual boot of Windows 11 and Arch Linux, with fast boot disabled. I've run this setup for the last half year and it has worked mostly okay, including switching between Ethernet and WiFi.

I've encountered this issue once before. I resolved it by resetting the router and restoring Arch Linux to a snapshot, but this solution is no longer effective. Any suggestions for finding the root cause of this problem and solving it properly?

Offline

#2 2023-05-08 13:23:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

If you don't think there're competing services (post it anyway!) also post your complete system journal for an affected boot: 

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

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2023-05-08 17:58:10

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

bluetooth.service                        | bluetooth.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
optimus-manager.service                  | graphical.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
reflector.service                        | multi-user.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants

The system journal can be found here: http://0x0.st/HZYi.txt. I see it's polluted by:

daemon[2827]: Command not supported

How do I find the culprit to this problem also?

Offline

#4 2023-05-08 19:21:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

"daemon" is likely some power management daemon for your notebook?

The network setup is a bit more complex than your run-off the mill internet.
There's a wired and a wifi lease in two different subnets (192.168.0.*/172.20.10.*) and there're the virtual devices from docker and containerd.

You first get a lease on

May 08 19:53:43 arch NetworkManager[431]: <info>  [1683568423.3569] dhcp4 (wlo1):   address 192.168.0.37

then an additional lease on

May 08 19:53:46 arch NetworkManager[431]: <info>  [1683568426.9563] dhcp4 (enp2s0):   address 192.168.0.196

and then reconnect the WiFi to

May 08 19:55:15 arch NetworkManager[431]: <info>  [1683568515.6100] dhcp4 (wlo1):   address 172.20.10.2

There's no obvious indicator for a flaky connection.
On what network do you experience the problem and what are the specific symptoms?
What if you simplify the stack and remove docker and containerd (as well as the power management tool) for the moment?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2023-05-08 19:44:27

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

seth wrote:

"daemon" is likely some power management daemon for your notebook?

Yes, I figured it out. It was razerdaemon specific for my laptop (Razer Blade 15). I've disabled it for now.

seth wrote:

On what network do you experience the problem and what are the specific symptoms?

I only experience it on my home network which uses a Zyxel EX5501 router is from my ISP. I've tried resetting it, and also deleting the NetworkManager data, but that doesn't resolve the issue.

The symptoms are as follows:

  • Immediately after connecting (Wifi or Ethernet) the internet connection works. It then stops working after ~10 seconds.

  • After 2-3 minutes the internet connection works again, but only for 10-15 seconds before it stops working again.

  • Repeat. All other networks work just fine, no issues. However, my home network is the only network I've connected to both wirelessly and with Ethernet.

Offline

#6 2023-05-08 19:51:09

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

What's the metric for "internet connection works" and "stops working"?
Can you 

ping -c1 _gateway
ping -c1 8.8.8.8
ping -c1 google.com

What if you don't connect the WiFi but only the RJ45?
What's the plan here to begin with? Bonding or fallover?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2023-05-08 20:03:27

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

seth wrote:

What's the metric for "internet connection works" and "stops working"?

If I ping google.com the packets go through "when it works" and gets dropped when it "stops working". When browsing the internet pages just get stuck loading. Right now I'm actually unable to get the connection to work at all though. 

~ 10s | 1 ❱ ping -c1 _gateway

PING _gateway (192.168.0.1) 56(84) bytes of data.
64 bytes from arch (192.168.0.1): icmp_seq=1 ttl=64 time=0.054 ms

--- _gateway ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.054/0.054/0.054/0.000 ms
~ ❱ ping -c1 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

~ 10s | 1 ❱ ping -c1 google.com

PING google.com(arn11s04-in-x0e.1e100.net (2a00:1450:400f:80b::200e)) 56 data bytes

--- google.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
~ | 2 ❱ ping google.com
ping: google.com: Temporary failure in name resolution
seth wrote:

What if you don't connect the WiFi but only the RJ45?

Plugging in the RJ45 I get the same issues. I've previously tried disabling the Wifi card entirely but it didn't resolve the issue. How do I ensure it's only using the wired Ethernet connection?

Offline

#8 2023-05-08 20:14:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

Remove the wifi profile from networkmanager.
You could ping the _gateway (ie. the router) but wer failing on the WAN connection - is this consisntent?

ping _gateway # let it run and see whether you get intermittent losses here as well

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2023-05-08 22:13:00

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

This is the result after deleting the system connections in /etc/NetworkManager/system-connections and then plugging in the ethernet cable:

system-connections 7.3s ❱ nmcli
tun0: connected (externally) to tun0
        "tun0"
        tun, sw, mtu 1310
        inet4 10.52.227.45/32
        route4 default metric 0
        route4 10.52.224.0/19 metric 0
        inet6 2001:700:302:11::21e/64
        inet6 fe80::c1cf:1682:ddf6:b007/64
        route6 2001:700:302:11::/64 metric 256
        route6 fe80::/64 metric 256
        route6 default metric 1

br-63b79177413d: connected (externally) to br-63b79177413d
        "br-63b79177413d"
        bridge, 02:42:89:B7:38:94, sw, mtu 1500
        inet4 172.28.0.1/16
        route4 172.28.0.0/16 metric 0
        inet6 fe80::42:89ff:feb7:3894/64
        route6 fe80::/64 metric 256

br-71d7bb25d4f1: connected (externally) to br-71d7bb25d4f1
        "br-71d7bb25d4f1"
        bridge, 02:42:3C:31:9B:A9, sw, mtu 1500
        inet4 172.19.0.1/16
        route4 172.19.0.0/16 metric 0
        inet6 fe80::42:3cff:fe31:9ba9/64
        route6 fe80::/64 metric 256

br-a6eab9103826: connected (externally) to br-a6eab9103826
        "br-a6eab9103826"
        bridge, 02:42:15:67:48:EA, sw, mtu 1500
        inet4 192.168.0.1/20
        route4 192.168.0.0/20 metric 0
        inet6 fe80::42:15ff:fe67:48ea/64
        route6 fe80::/64 metric 256

br-c5b192f60734: connected (externally) to br-c5b192f60734
        "br-c5b192f60734"
        bridge, 02:42:51:0C:AA:E9, sw, mtu 1500
        inet4 192.168.32.1/20
        route4 192.168.32.0/20 metric 0
        inet6 fe80::42:51ff:fe0c:aae9/64
        route6 fe80::/64 metric 256

br-fbf9c8451698: connected (externally) to br-fbf9c8451698
        "br-fbf9c8451698"
        bridge, 02:42:E5:EF:F9:35, sw, mtu 1500
        inet4 172.30.0.1/16
        route4 172.30.0.0/16 metric 0
        inet6 fe80::42:e5ff:feef:f935/64
        route6 fe80::/64 metric 256

br-ff5c72b69bd3: connected (externally) to br-ff5c72b69bd3
        "br-ff5c72b69bd3"
        bridge, 02:42:7B:C7:43:FB, sw, mtu 1500
        inet4 192.168.16.1/20
        route4 192.168.16.0/20 metric 0
        inet6 fe80::42:7bff:fec7:43fb/64
        route6 fe80::/64 metric 256

docker0: connected (externally) to docker0
        "docker0"
        bridge, 02:42:9D:8A:80:01, sw, mtu 1500
        inet4 172.17.0.1/16
        route4 172.17.0.0/16 metric 0
        inet6 fe80::42:9dff:fe8a:8001/64
        route6 fe80::/64 metric 256

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128
        route6 ::1/128 metric 256

br-11a9ad5ff453: connected (externally) to br-11a9ad5ff453
        "br-11a9ad5ff453"
        bridge, 02:42:54:A9:E6:33, sw, mtu 1500
        inet4 172.29.0.1/16
        route4 172.29.0.0/16 metric 0

br-41cd16dd3663: connected (externally) to br-41cd16dd3663
        "br-41cd16dd3663"
        bridge, 02:42:46:58:3B:B5, sw, mtu 1500
        inet4 172.27.0.1/16
        route4 172.27.0.0/16 metric 0

No packets dropped when pinging the gateway: 

system-connections 1.2s ❱ ping _gateway
PING _gateway (192.168.0.1) 56(84) bytes of data.
64 bytes from arch (192.168.0.1): icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from arch (192.168.0.1): icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from arch (192.168.0.1): icmp_seq=3 ttl=64 time=0.024 ms
64 bytes from arch (192.168.0.1): icmp_seq=4 ttl=64 time=0.074 ms
64 bytes from arch (192.168.0.1): icmp_seq=5 ttl=64 time=0.067 ms
64 bytes from arch (192.168.0.1): icmp_seq=6 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=7 ttl=64 time=0.066 ms
64 bytes from arch (192.168.0.1): icmp_seq=8 ttl=64 time=0.127 ms
64 bytes from arch (192.168.0.1): icmp_seq=9 ttl=64 time=0.023 ms
64 bytes from arch (192.168.0.1): icmp_seq=10 ttl=64 time=0.078 ms
64 bytes from arch (192.168.0.1): icmp_seq=11 ttl=64 time=0.064 ms
64 bytes from arch (192.168.0.1): icmp_seq=12 ttl=64 time=0.027 ms
64 bytes from arch (192.168.0.1): icmp_seq=13 ttl=64 time=0.037 ms
64 bytes from arch (192.168.0.1): icmp_seq=14 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=15 ttl=64 time=0.096 ms
64 bytes from arch (192.168.0.1): icmp_seq=16 ttl=64 time=0.067 ms
64 bytes from arch (192.168.0.1): icmp_seq=17 ttl=64 time=0.064 ms
64 bytes from arch (192.168.0.1): icmp_seq=18 ttl=64 time=0.064 ms
64 bytes from arch (192.168.0.1): icmp_seq=19 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=20 ttl=64 time=0.041 ms
64 bytes from arch (192.168.0.1): icmp_seq=21 ttl=64 time=0.030 ms
64 bytes from arch (192.168.0.1): icmp_seq=22 ttl=64 time=0.027 ms
64 bytes from arch (192.168.0.1): icmp_seq=23 ttl=64 time=0.067 ms
64 bytes from arch (192.168.0.1): icmp_seq=24 ttl=64 time=0.065 ms
64 bytes from arch (192.168.0.1): icmp_seq=25 ttl=64 time=0.071 ms
64 bytes from arch (192.168.0.1): icmp_seq=26 ttl=64 time=0.031 ms
64 bytes from arch (192.168.0.1): icmp_seq=27 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=28 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=29 ttl=64 time=0.070 ms
64 bytes from arch (192.168.0.1): icmp_seq=30 ttl=64 time=0.065 ms
64 bytes from arch (192.168.0.1): icmp_seq=31 ttl=64 time=0.029 ms
64 bytes from arch (192.168.0.1): icmp_seq=32 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=33 ttl=64 time=0.070 ms
64 bytes from arch (192.168.0.1): icmp_seq=34 ttl=64 time=0.038 ms
64 bytes from arch (192.168.0.1): icmp_seq=35 ttl=64 time=0.085 ms
64 bytes from arch (192.168.0.1): icmp_seq=36 ttl=64 time=0.065 ms
64 bytes from arch (192.168.0.1): icmp_seq=37 ttl=64 time=0.066 ms
64 bytes from arch (192.168.0.1): icmp_seq=38 ttl=64 time=0.039 ms
64 bytes from arch (192.168.0.1): icmp_seq=39 ttl=64 time=0.031 ms
64 bytes from arch (192.168.0.1): icmp_seq=40 ttl=64 time=0.054 ms
64 bytes from arch (192.168.0.1): icmp_seq=41 ttl=64 time=0.024 ms
64 bytes from arch (192.168.0.1): icmp_seq=42 ttl=64 time=0.036 ms
64 bytes from arch (192.168.0.1): icmp_seq=43 ttl=64 time=0.071 ms
64 bytes from arch (192.168.0.1): icmp_seq=44 ttl=64 time=0.030 ms
64 bytes from arch (192.168.0.1): icmp_seq=45 ttl=64 time=0.091 ms
64 bytes from arch (192.168.0.1): icmp_seq=46 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=47 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=48 ttl=64 time=0.025 ms
64 bytes from arch (192.168.0.1): icmp_seq=49 ttl=64 time=0.071 ms
64 bytes from arch (192.168.0.1): icmp_seq=50 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=51 ttl=64 time=0.074 ms
64 bytes from arch (192.168.0.1): icmp_seq=52 ttl=64 time=0.023 ms
64 bytes from arch (192.168.0.1): icmp_seq=53 ttl=64 time=0.067 ms
64 bytes from arch (192.168.0.1): icmp_seq=54 ttl=64 time=0.069 ms
64 bytes from arch (192.168.0.1): icmp_seq=55 ttl=64 time=0.052 ms
64 bytes from arch (192.168.0.1): icmp_seq=56 ttl=64 time=0.075 ms
64 bytes from arch (192.168.0.1): icmp_seq=57 ttl=64 time=0.026 ms
64 bytes from arch (192.168.0.1): icmp_seq=58 ttl=64 time=0.076 ms
64 bytes from arch (192.168.0.1): icmp_seq=59 ttl=64 time=0.072 ms
64 bytes from arch (192.168.0.1): icmp_seq=60 ttl=64 time=0.071 ms
64 bytes from arch (192.168.0.1): icmp_seq=61 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=62 ttl=64 time=0.086 ms
64 bytes from arch (192.168.0.1): icmp_seq=63 ttl=64 time=0.068 ms
64 bytes from arch (192.168.0.1): icmp_seq=64 ttl=64 time=0.067 ms
64 bytes from arch (192.168.0.1): icmp_seq=65 ttl=64 time=0.054 ms
64 bytes from arch (192.168.0.1): icmp_seq=66 ttl=64 time=0.022 ms
64 bytes from arch (192.168.0.1): icmp_seq=67 ttl=64 time=0.070 ms
64 bytes from arch (192.168.0.1): icmp_seq=68 ttl=64 time=0.024 ms
64 bytes from arch (192.168.0.1): icmp_seq=69 ttl=64 time=0.025 ms
64 bytes from arch (192.168.0.1): icmp_seq=70 ttl=64 time=0.092 ms
64 bytes from arch (192.168.0.1): icmp_seq=71 ttl=64 time=0.027 ms
64 bytes from arch (192.168.0.1): icmp_seq=72 ttl=64 time=0.021 ms
^C
--- _gateway ping statistics ---
72 packets transmitted, 72 received, 0% packet loss, time 71935ms
rtt min/avg/max/mdev = 0.021/0.057/0.127/0.022 ms

The issue is no longer intermittent. It just doesn't work at all anymore: 

~ ❱ ping google.com
PING google.com(arn09s23-in-x0e.1e100.net (2a00:1450:400f:802::200e)) 56 data bytes
^C
--- google.com ping statistics ---
37 packets transmitted, 0 received, 100% packet loss, time 36492ms
~ ❱ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25332ms

Last edited by hawkis (2023-05-08 22:13:35)

Offline

#10 2023-05-08 22:29:19

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

ip a
ip r
ip r get 192.168.0.1
ip r get 8.8.8.8

but from the nmcli it seems the tun0 is the default gateway - which didn't show up in the journal you posted?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2023-05-09 06:17:22

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

seth wrote:
ip a
ip r
ip r get 192.168.0.1
ip r get 8.8.8.8

but from the nmcli it seems the tun0 is the default gateway - which didn't show up in the journal you posted?

In the journal I posted I used Wifi. Now I’ve removed the system connection and tried Ethernet as you suggested, so I’d assume that’s why.

Offline

#12 2023-05-09 06:19:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

You understand that this indicates a VPN being used which is *VERY* relevant here?
Post the output of the 4 commands.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2023-05-09 06:49:00

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

seth wrote:

You understand that this indicates a VPN being used which is *VERY* relevant here?

My apoligies, I forgot I was on the school VPN. I've turned off the VPN.

Now I have the intermittent issues again, where it works for 10-15 seconds, then stops working for a while (several minutes) before working for 10-15 seconds again. Here's the result of pinging google: 

~ ❱ ping google.com
PING google.com (216.58.207.206) 56(84) bytes of data.
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=112 ttl=52 time=2563 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=113 ttl=52 time=1550 ms
ping: Warning: time of day goes back (-433368us), taking countermeasures
ping: Warning: time of day goes back (-405746us), taking countermeasures
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=114 ttl=52 time=0.000 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=115 ttl=52 time=14.5 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=116 ttl=52 time=15.2 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=117 ttl=52 time=15.7 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=118 ttl=52 time=15.2 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=119 ttl=52 time=15.4 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=120 ttl=52 time=15.7 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=121 ttl=52 time=15.6 ms
64 bytes from arn11s04-in-f14.1e100.net (216.58.207.206): icmp_seq=122 ttl=52 time=15.1 ms
^C
--- google.com ping statistics ---
338 packets transmitted, 11 received, 96.7456% packet loss, time 341216ms
rtt min/avg/max/mdev = 0.000/385.049/2563.256/817.076 ms, pipe 3

I get "Warning: time of day goes back" which I've never gotten before.

Post the output of the 4 commands.

With VPN OFF: 

~ ❱ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 98:bb:1e:1c:4b:e1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.196/24 brd 192.168.0.255 scope global dynamic noprefixroute enp2s0
       valid_lft 86346sec preferred_lft 86346sec
    inet6 fde1:a95f:1e43:4cbb:1a79:5201:38a0:26d7/64 scope global dynamic noprefixroute 
       valid_lft 1762sec preferred_lft 1762sec
    inet6 fe80::92c9:e8d0:23be:440d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 96:83:b9:f6:18:07 brd ff:ff:ff:ff:ff:ff permaddr 3c:58:c2:6f:1f:6c
    altname wlp0s20f3
4: br-7a882774d2b5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:81:0e:49:31 brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.1/16 brd 172.20.255.255 scope global br-7a882774d2b5
       valid_lft forever preferred_lft forever
5: br-d05909bf31b3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:34:d9:48:19 brd ff:ff:ff:ff:ff:ff
    inet 192.168.64.1/20 brd 192.168.79.255 scope global br-d05909bf31b3
       valid_lft forever preferred_lft forever
6: br-a7770eb02811: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:46:b5:a3:80 brd ff:ff:ff:ff:ff:ff
    inet 172.21.0.1/16 brd 172.21.255.255 scope global br-a7770eb02811
       valid_lft forever preferred_lft forever
7: br-fed2bbb7709a: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:2e:6b:61:bd brd ff:ff:ff:ff:ff:ff
    inet 172.23.0.1/16 brd 172.23.255.255 scope global br-fed2bbb7709a
       valid_lft forever preferred_lft forever
8: br-ff5c72b69bd3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:0b:c7:8a:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.16.1/20 brd 192.168.31.255 scope global br-ff5c72b69bd3
       valid_lft forever preferred_lft forever
    inet6 fe80::42:bff:fec7:8a66/64 scope link 
       valid_lft forever preferred_lft forever
9: br-4be0748823e9: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:fe:94:e8:09 brd ff:ff:ff:ff:ff:ff
    inet 172.24.0.1/16 brd 172.24.255.255 scope global br-4be0748823e9
       valid_lft forever preferred_lft forever
10: br-71d7bb25d4f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:18:f7:a2:9f brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-71d7bb25d4f1
       valid_lft forever preferred_lft forever
    inet6 fe80::42:18ff:fef7:a29f/64 scope link 
       valid_lft forever preferred_lft forever
11: br-a6eab9103826: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:47:a2:6c:48 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.1/20 brd 192.168.15.255 scope global br-a6eab9103826
       valid_lft forever preferred_lft forever
    inet6 fe80::42:47ff:fea2:6c48/64 scope link 
       valid_lft forever preferred_lft forever
12: br-b8f65ebbdc56: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:cb:2d:d6:90 brd ff:ff:ff:ff:ff:ff
    inet 172.26.0.1/16 brd 172.26.255.255 scope global br-b8f65ebbdc56
       valid_lft forever preferred_lft forever
13: br-c173b0917a05: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:55:1c:d1:b4 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-c173b0917a05
       valid_lft forever preferred_lft forever
14: br-db6671d5700a: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:7c:55:40:88 brd ff:ff:ff:ff:ff:ff
    inet 172.25.0.1/16 brd 172.25.255.255 scope global br-db6671d5700a
       valid_lft forever preferred_lft forever
15: br-c5b192f60734: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:5b:2e:4b:16 brd ff:ff:ff:ff:ff:ff
    inet 192.168.32.1/20 brd 192.168.47.255 scope global br-c5b192f60734
       valid_lft forever preferred_lft forever
    inet6 fe80::42:5bff:fe2e:4b16/64 scope link 
       valid_lft forever preferred_lft forever
16: br-dafb6a30b63b: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:9b:15:16:32 brd ff:ff:ff:ff:ff:ff
    inet 192.168.48.1/20 brd 192.168.63.255 scope global br-dafb6a30b63b
       valid_lft forever preferred_lft forever
17: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:60:6b:da:c2 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
18: br-11a9ad5ff453: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:cc:18:17:9d brd ff:ff:ff:ff:ff:ff
    inet 172.29.0.1/16 brd 172.29.255.255 scope global br-11a9ad5ff453
       valid_lft forever preferred_lft forever
19: br-41cd16dd3663: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:f3:78:80:10 brd ff:ff:ff:ff:ff:ff
    inet 172.27.0.1/16 brd 172.27.255.255 scope global br-41cd16dd3663
       valid_lft forever preferred_lft forever
20: br-63b79177413d: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:fb:53:d0:d6 brd ff:ff:ff:ff:ff:ff
    inet 172.28.0.1/16 brd 172.28.255.255 scope global br-63b79177413d
       valid_lft forever preferred_lft forever
21: br-8f8f01fccb2f: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:76:51:32:60 brd ff:ff:ff:ff:ff:ff
    inet 172.22.0.1/16 brd 172.22.255.255 scope global br-8f8f01fccb2f
       valid_lft forever preferred_lft forever
22: br-9a29a9829683: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:4c:3b:ea:11 brd ff:ff:ff:ff:ff:ff
    inet 172.31.0.1/16 brd 172.31.255.255 scope global br-9a29a9829683
       valid_lft forever preferred_lft forever
23: br-fbf9c8451698: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:91:58:c4:2b brd ff:ff:ff:ff:ff:ff
    inet 172.30.0.1/16 brd 172.30.255.255 scope global br-fbf9c8451698
       valid_lft forever preferred_lft forever
25: veth9f3d254@if24: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-ff5c72b69bd3 state UP group default 
    link/ether ba:00:3c:55:a7:40 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::b800:3cff:fe55:a740/64 scope link 
       valid_lft forever preferred_lft forever
27: veth342dea9@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-c5b192f60734 state UP group default 
    link/ether 8e:15:20:c4:f2:a6 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::8c15:20ff:fec4:f2a6/64 scope link 
       valid_lft forever preferred_lft forever
29: vethe018c04@if28: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-a6eab9103826 state UP group default 
    link/ether 92:42:a8:1f:f6:41 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::9042:a8ff:fe1f:f641/64 scope link 
       valid_lft forever preferred_lft forever
31: vethca5cce1@if30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-71d7bb25d4f1 state UP group default 
    link/ether f2:3e:2d:fe:dd:fa brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::f03e:2dff:fefe:ddfa/64 scope link 
       valid_lft forever preferred_lft forever
~ ❱ ip r
default via 192.168.0.1 dev enp2s0 proto dhcp src 192.168.0.196 metric 100 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.18.0.0/16 dev br-c173b0917a05 proto kernel scope link src 172.18.0.1 linkdown 
172.19.0.0/16 dev br-71d7bb25d4f1 proto kernel scope link src 172.19.0.1 
172.20.0.0/16 dev br-7a882774d2b5 proto kernel scope link src 172.20.0.1 linkdown 
172.21.0.0/16 dev br-a7770eb02811 proto kernel scope link src 172.21.0.1 linkdown 
172.22.0.0/16 dev br-8f8f01fccb2f proto kernel scope link src 172.22.0.1 linkdown 
172.23.0.0/16 dev br-fed2bbb7709a proto kernel scope link src 172.23.0.1 linkdown 
172.24.0.0/16 dev br-4be0748823e9 proto kernel scope link src 172.24.0.1 linkdown 
172.25.0.0/16 dev br-db6671d5700a proto kernel scope link src 172.25.0.1 linkdown 
172.26.0.0/16 dev br-b8f65ebbdc56 proto kernel scope link src 172.26.0.1 linkdown 
172.27.0.0/16 dev br-41cd16dd3663 proto kernel scope link src 172.27.0.1 linkdown 
172.28.0.0/16 dev br-63b79177413d proto kernel scope link src 172.28.0.1 linkdown 
172.29.0.0/16 dev br-11a9ad5ff453 proto kernel scope link src 172.29.0.1 linkdown 
172.30.0.0/16 dev br-fbf9c8451698 proto kernel scope link src 172.30.0.1 linkdown 
172.31.0.0/16 dev br-9a29a9829683 proto kernel scope link src 172.31.0.1 linkdown 
192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.196 metric 100 
192.168.0.0/20 dev br-a6eab9103826 proto kernel scope link src 192.168.0.1 
192.168.16.0/20 dev br-ff5c72b69bd3 proto kernel scope link src 192.168.16.1 
192.168.32.0/20 dev br-c5b192f60734 proto kernel scope link src 192.168.32.1 
192.168.48.0/20 dev br-dafb6a30b63b proto kernel scope link src 192.168.48.1 linkdown 
192.168.64.0/20 dev br-d05909bf31b3 proto kernel scope link src 192.168.64.1 linkdown
~ ❱ ip r get 192.168.0.1
local 192.168.0.1 dev lo src 192.168.0.1 uid 1000 
    cache <local> 
~ ❱ ip r get 8.8.8.8
8.8.8.8 via 192.168.0.1 dev enp2s0 src 192.168.0.196 uid 1000 
    cache

Offline

#14 2023-05-09 07:01:01

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

The system time adjusted (likely because NTP kicked in once you removed the VPN and got an actual WAN connection)
This kinda skews the ping results, how's the ping behavior now?
Do the time jumps still happen?

Also

seth wrote:

… simplify the stack and remove docker and containerd (as well as the power management tool) for the moment

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2023-05-09 07:16:25

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

Thank you. Removing docker and containerd completely resolved the issue. I was reluctant to removing it because I need it for course work. Should I try to reinstall it? Why would this cause problems on one specific network, but not others?

Offline

#16 2023-05-09 07:31:09

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

These here collide

192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.196 metric 100 
192.168.0.0/20 dev br-a6eab9103826 proto kernel scope link src 192.168.0.1

and the routing is off (as apparently a result) and you seem to have later on (?) changed the docker config to some 172.*.0.0/16 segment (perhaps for that reason) - but this change didn't affect existing containers.

The other networks probably operate on a disjunct segment.

because I need it for course work

You may live with it, but you "need" docker like you "need" a furuncle…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2023-05-09 07:36:39

hawkis
Member
Registered: 2023-01-04
Posts: 13

Re: Intermittent internet connection on specific network

seth wrote:

you seem to have later on (?) changed the docker config to some 172.*.0.0/16 segment (perhaps for that reason)

No, I haven't touched the network config.

seth wrote:

but this change didn't affect existing containers.

So if I reinstall docker and recreate the containers, the issue might be resolved?

seth wrote:

You may live with it, but you "need" docker like you "need" a furuncle…

It's a requirement in the assignment. Not my choice.

Offline

#18 2023-05-09 07:47:06

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,337

Re: Intermittent internet connection on specific network

No, I haven't touched the network config.

It would be the/a docker config, but apparently it's just dockers default behavior when wasting subnets for containers.


might be resolved

A lot of things "might" be and it'll depend on what subnet those containers end up with.

If you don't have 20 containers around you can try to simply clean-up first, "docker system prune", https://wiki.archlinux.org/title/Docker … and_images


Here're some links on how to change the docker subnet config:
https://www.refocusdata.com/fix-docker- … l-subnets/
https://webwork.blog/docker-subnetze-andern/ (german)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB