Does anyone else (using Plasma 6) see "Limited Connectivity" notifications with Wi-Fi and Ethernet enabled?

Ask Fedora
, , ,
1

As described at:

…the initial premise is:

  2. I can also now reproduce this on my Framework 16 (laptop) [1] with mostly Category 8 RJ-45 802.3 enabled, alongside 802.11ac-2013, connected to my Teltonika RUTXR1 AP. When I disable .11 from the plasmoid, the error disappears. Is this a bug?

I’ve since been informed that the OS performs more of the configuration than the DE does, regarding network connectivity verification.

  1. frame.work/gb/en/products/ethernet-expansion-card ↩︎

1 Like
2

(Just to mirror here what I said in the KDE forum): I too have indeed seen these notifications when there was no problem accessing the internet in general.

1 Like
3

I just see it when I am on VPN mostly and ignoring it. Seems it doesn’t affect connections at all. I didn’t see it for a month and bow it is back again

4

@thephatlee, what VPN? (flathub app/com.protonvpn.www/x86_64/stable --commit=199c282fd41539e3396f6fddce53558dde558f5a130f0457c0d90857a70fbd95)?

5

This was always when using nordVPN. Proton is all good nothing on that side

1 Like
6

See also:

1 Like
7

@vgaetera, my ISP (Utility Warehouse) doesn’t support IPv6 [1] even though their official Techicolour DGA2231 modem + router that I utilise as my LAN gateway does. Consequently, if I’ve understood correctly, I doubt that NetworkManager/-/issues/116#note_2560729 applies. Otherwise, would “a level=TRACE log” be of use…? [2]

I’m honoured you’ve so much expectation of my knowledge, but that’s a little beyond my ability to confidently comprehend.

  1. peeringdb.com/asn/51553 ↩︎

  2. cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf?id=8dc64c7bddb0135a12c1a1e4cefc959407d227a6#n34 [3] ↩︎

  3. gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/116#note_112874 ↩︎

1 Like
8

I had a problem with a past ISP, where their network didn’t support IPv6, but their router did issue IPv6 DNS addresses to local devices via DHCP (and possibly advertise routes, though I didn’t keep detailed enough records to be sure).

This caused me material issues (some Android apps would insist on trying to connect to remote hosts using IPv6, and never succeed). I fixed it by disabling IPv6 DNS on the router.

Fom the issue you linked to, I wouldn’t be surprised if that config would have caused me to see failed connectivity checks had I used Fedora at the time.

1 Like
9

@pg-tips, I’ve no desire to lose IPv6 DHCP, because it’s useful: :frowning:

However, I’ll attempt to remember to test when I can. Thanks.

1 Like
10

Here’s a simple way to troubleshoot connectivity check:

curl -v http://fedoraproject.org/static/hotspot.txt

You can also specify the interface name and address family.
However, it may be difficult to detect a transient issue.

1 Like
11

@vgaetera, that appears to return OK, even when the problem is shown:

Screenshot_20250811_104125
Screenshot_20250811_1041252561×801 270 KB

1 Like
12

There’s more relevant info in the log, try monitoring it for some time:

sudo nmcli general logging level TRACE domains ALL
journalctl --no-hostname -f -u NetworkManager.service -g connectivity
1 Like
13

@vgaetera, I first ran those commands without my 802.3 cable connected, and waited for > 15 s. It produced no logs. When I connected the cable, it produced some expected connection logs, but also began to produce periodic connection verification logs thereafter. They would come in batches of > 8, approximately every 20 s.

All of them indicated success, until I left it for > 5 minutes, after which I saw some logs that appear very relevant. Unfortunately, I’ve somehow been unable to catch the notification itself recur, probably by mere chance.

Due to Discourse’s character count restrictions, I’ve solely submitted the presumably erroneous section of the logs undermentioned:

Aug 12 18:45:00 NetworkManager[2407]: <trace> [1755020700.5083] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] start check (seq:290, periodic-check)
Aug 12 18:45:00 NetworkManager[2407]: <debug> [1755020700.5085] connectivity: (wlp1s0,IPv4,290) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:45:00 NetworkManager[2407]: <trace> [1755020700.5290] connectivity: (wlp1s0,IPv4,290) set curl resolve list to 'fedoraproject.org:80:140.211.169.196,8.43.85.73,34.211.44.206,38.145.32.20,38.145.32.21,152.19.134.198,67.219.144.68,152.19.134.142,8.43.85.67'
Aug 12 18:45:00 NetworkManager[2407]: <debug> [1755020700.8164] connectivity: (wlp1s0,IPv4,290) check completed: FULL; expected response
Aug 12 18:45:00 NetworkManager[2407]: <trace> [1755020700.8165] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] complete check (seq:290, state:FULL)
Aug 12 18:45:00 NetworkManager[2407]: <trace> [1755020700.8165] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299691 milliseconds (300 seconds interval)
Aug 12 18:47:56 NetworkManager[2407]: <trace> [1755020876.0291] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 300000 milliseconds (300 seconds interval)
Aug 12 18:47:56 NetworkManager[2407]: <trace> [1755020876.0292] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:291, periodic-check)
Aug 12 18:47:56 NetworkManager[2407]: <debug> [1755020876.0293] connectivity: (enp193s0f3u2u1,IPv6,291) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:47:56 NetworkManager[2407]: <trace> [1755020876.0486] connectivity: (enp193s0f3u2u1,IPv6,291) set curl resolve list to 'fedoraproject.org:80:2620:52:6:1121:bead:cafe:feed:fed6,2600:2701:4000:5211:dead:beef:fe:fed3,2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:3:1:dead:beef:cafe:fed7,2620:52:3:1:dead:beef:cafe:fed6,2604:1580:fe00:0:dead:beef:cafe:fed1,2620:52:6:1121:bead:cafe:feed:fed5,2605:bc80:3010:600:dead:beef:cafe:fed9'
Aug 12 18:47:56 NetworkManager[2407]: <debug> [1755020876.0491] connectivity: (enp193s0f3u2u1,IPv6,291) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:47:56 NetworkManager[2407]: <trace> [1755020876.0492] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:291, state:LIMITED)
Aug 12 18:47:56 NetworkManager[2407]: <trace> [1755020876.0492] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 299980 milliseconds (300 seconds interval)
Aug 12 18:48:26 NetworkManager[2407]: <trace> [1755020906.3281] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:26 NetworkManager[2407]: <trace> [1755020906.3281] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:292, periodic-check)
Aug 12 18:48:26 NetworkManager[2407]: <debug> [1755020906.3282] connectivity: (enp193s0f3u2u1,IPv4,292) skip connectivity check due to no global route configured
Aug 12 18:48:26 NetworkManager[2407]: <debug> [1755020906.3282] connectivity: (enp193s0f3u2u1,IPv4,292) check completed: LIMITED; no global route configured
Aug 12 18:48:26 NetworkManager[2407]: <trace> [1755020906.3282] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:292, state:LIMITED)
Aug 12 18:48:26 NetworkManager[2407]: <trace> [1755020906.3282] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2680] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] start check (seq:293, periodic-check)
Aug 12 18:48:27 NetworkManager[2407]: <debug> [1755020907.2681] connectivity: (p2p-dev-wlp1s0,IPv4,293) start fake request (fake result)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] start check (seq:294, periodic-check)
Aug 12 18:48:27 NetworkManager[2407]: <debug> [1755020907.2681] connectivity: (p2p-dev-wlp1s0,IPv6,294) start fake request (fake result)
Aug 12 18:48:27 NetworkManager[2407]: <debug> [1755020907.2681] connectivity: (p2p-dev-wlp1s0,IPv4,293) check completed: FAKE; fake result
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] complete check (seq:293, state:FAKE)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:27 NetworkManager[2407]: <debug> [1755020907.2681] connectivity: (p2p-dev-wlp1s0,IPv6,294) check completed: FAKE; fake result
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2682] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] complete check (seq:294, state:FAKE)
Aug 12 18:48:27 NetworkManager[2407]: <trace> [1755020907.2682] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:30 NetworkManager[2407]: <trace> [1755020910.5083] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:48:30 NetworkManager[2407]: <trace> [1755020910.5084] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] start check (seq:295, periodic-check)
Aug 12 18:48:30 NetworkManager[2407]: <debug> [1755020910.5085] connectivity: (wlp1s0,IPv6,295) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:48:30 NetworkManager[2407]: <trace> [1755020910.5093] connectivity: (wlp1s0,IPv6,295) set curl resolve list to 'fedoraproject.org:80:2a05:d014:10:7803:e679:200f:1d55:a3d,2604:1580:fe00:0:dead:beef:cafe:fed1,2001:4178:2:1269::fed2,2a05:d01c:c6a:cc01:80a4:89a8:76d0:aa54,2a05:d014:10:7803:142c:f27e:9113:eb70,2600:2701:4000:5211:dead:beef:fe:fed3,2605:bc80:3010:600:dead:beef:cafe:fed9'Aug 12 18:48:30 NetworkManager[2407]: <debug> [1755020910.5096] connectivity: (wlp1s0,IPv6,295) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:48:30 NetworkManager[2407]: <trace> [1755020910.5096] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] complete check (seq:295, state:LIMITED)
Aug 12 18:48:30 NetworkManager[2407]: <trace> [1755020910.5096] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299998 milliseconds (300 seconds interval)
Aug 12 18:50:00 NetworkManager[2407]: <trace> [1755021000.5084] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:50:00 NetworkManager[2407]: <trace> [1755021000.5085] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] start check (seq:296, periodic-check)
Aug 12 18:50:00 NetworkManager[2407]: <debug> [1755021000.5085] connectivity: (wlp1s0,IPv4,296) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:50:00 NetworkManager[2407]: <trace> [1755021000.5274] connectivity: (wlp1s0,IPv4,296) set curl resolve list to 'fedoraproject.org:80:8.43.85.67,8.43.85.73,34.211.44.206,152.19.134.142,140.211.169.196,67.219.144.68,152.19.134.198,38.145.32.20,38.145.32.21'
Aug 12 18:50:00 NetworkManager[2407]: <debug> [1755021000.7295] connectivity: (wlp1s0,IPv4,296) check completed: FULL; expected response
Aug 12 18:50:00 NetworkManager[2407]: <trace> [1755021000.7296] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] complete check (seq:296, state:FULL)
Aug 12 18:50:00 NetworkManager[2407]: <trace> [1755021000.7296] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299778 milliseconds (300 seconds interval)
Aug 12 18:52:56 NetworkManager[2407]: <trace> [1755021176.0294] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 300000 milliseconds (300 seconds interval)
Aug 12 18:52:56 NetworkManager[2407]: <trace> [1755021176.0295] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:297, periodic-check)
Aug 12 18:52:56 NetworkManager[2407]: <debug> [1755021176.0297] connectivity: (enp193s0f3u2u1,IPv6,297) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:52:56 NetworkManager[2407]: <trace> [1755021176.0481] connectivity: (enp193s0f3u2u1,IPv6,297) set curl resolve list to 'fedoraproject.org:80:2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:6:1121:bead:cafe:feed:fed5,2620:52:3:1:dead:beef:cafe:fed7,2620:52:6:1121:bead:cafe:feed:fed6,2600:2701:4000:5211:dead:beef:fe:fed3,2604:1580:fe00:0:dead:beef:cafe:fed1,2605:bc80:3010:600:dead:beef:cafe:fed9,2620:52:3:1:dead:beef:cafe:fed6'
Aug 12 18:52:56 NetworkManager[2407]: <debug> [1755021176.0488] connectivity: (enp193s0f3u2u1,IPv6,297) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:52:56 NetworkManager[2407]: <trace> [1755021176.0488] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:297, state:LIMITED)
Aug 12 18:52:56 NetworkManager[2407]: <trace> [1755021176.0488] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 299980 milliseconds (300 seconds interval)
Aug 12 18:53:26 NetworkManager[2407]: <trace> [1755021206.3277] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 300000 milliseconds (300 seconds interval)
Aug 12 18:53:26 NetworkManager[2407]: <trace> [1755021206.3278] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:298, periodic-check)
Aug 12 18:53:26 NetworkManager[2407]: <debug> [1755021206.3278] connectivity: (enp193s0f3u2u1,IPv4,298) skip connectivity check due to no global route configured
Aug 12 18:53:26 NetworkManager[2407]: <debug> [1755021206.3279] connectivity: (enp193s0f3u2u1,IPv4,298) check completed: LIMITED; no global route configured
Aug 12 18:53:26 NetworkManager[2407]: <trace> [1755021206.3279] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:298, state:LIMITED)
Aug 12 18:53:26 NetworkManager[2407]: <trace> [1755021206.3279] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 300000 milliseconds (300 seconds interval)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2680] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] start check (seq:299, periodic-check)
Aug 12 18:53:27 NetworkManager[2407]: <debug> [1755021207.2681] connectivity: (p2p-dev-wlp1s0,IPv4,299) start fake request (fake result)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] start check (seq:300, periodic-check)
Aug 12 18:53:27 NetworkManager[2407]: <debug> [1755021207.2681] connectivity: (p2p-dev-wlp1s0,IPv6,300) start fake request (fake result)
Aug 12 18:53:27 NetworkManager[2407]: <debug> [1755021207.2681] connectivity: (p2p-dev-wlp1s0,IPv4,299) check completed: FAKE; fake result
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] complete check (seq:299, state:FAKE)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2681] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv4] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:53:27 NetworkManager[2407]: <debug> [1755021207.2682] connectivity: (p2p-dev-wlp1s0,IPv6,300) check completed: FAKE; fake result
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2682] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] complete check (seq:300, state:FAKE)
Aug 12 18:53:27 NetworkManager[2407]: <trace> [1755021207.2682] device[7b44c493d07fa7f8] (p2p-dev-wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299999 milliseconds (300 seconds interval)
Aug 12 18:53:30 NetworkManager[2407]: <trace> [1755021210.5079] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 300000 milliseconds (300 seconds interval)
Aug 12 18:53:30 NetworkManager[2407]: <trace> [1755021210.5080] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] start check (seq:301, periodic-check)
Aug 12 18:53:30 NetworkManager[2407]: <debug> [1755021210.5081] connectivity: (wlp1s0,IPv6,301) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:53:30 NetworkManager[2407]: <trace> [1755021210.5288] connectivity: (wlp1s0,IPv6,301) set curl resolve list to 'fedoraproject.org:80:2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:6:1121:bead:cafe:feed:fed5,2604:1580:fe00:0:dead:beef:cafe:fed1,2605:bc80:3010:600:dead:beef:cafe:fed9,2620:52:3:1:dead:beef:cafe:fed6,2600:2701:4000:5211:dead:beef:fe:fed3,2620:52:3:1:dead:beef:cafe:fed7,2620:52:6:1121:bead:cafe:feed:fed6'
Aug 12 18:53:30 NetworkManager[2407]: <debug> [1755021210.5293] connectivity: (wlp1s0,IPv6,301) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:53:30 NetworkManager[2407]: <trace> [1755021210.5293] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] complete check (seq:301, state:LIMITED)
Aug 12 18:53:30 NetworkManager[2407]: <trace> [1755021210.5293] device[73109eee83515e7b] (wlp1s0): connectivity: [IPv6] periodic-check: re-scheduled in 299978 milliseconds (300 seconds interval)

However, part of the start is of interest:

RokeJulianLockhart@Beedell:~$ sudo nmcli general logging level TRACE domains ALL
journalctl --no-hostname -f -u NetworkManager.service -g connectivity
Place your right index finger on the fingerprint reader
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3341] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 1000 milliseconds (1 seconds interval)
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3341] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:258, periodic-check)
Aug 12 18:34:24 NetworkManager[2407]: <debug> [1755020064.3341] connectivity: (enp193s0f3u2u1,IPv4,258) skip connectivity check due to no IP address configured
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3341] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 1000 milliseconds (1 seconds interval)
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3341] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:259, periodic-check)
Aug 12 18:34:24 NetworkManager[2407]: <debug> [1755020064.3341] connectivity: (enp193s0f3u2u1,IPv6,259) skip connectivity check due to no IP address configured
Aug 12 18:34:24 NetworkManager[2407]: <debug> [1755020064.3344] connectivity: (enp193s0f3u2u1,IPv4,258) check completed: NONE; no IP address configured
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3344] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:258, state:NONE)
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3344] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 1999 milliseconds (2 seconds interval)
Aug 12 18:34:24 NetworkManager[2407]: <debug> [1755020064.3344] connectivity: (enp193s0f3u2u1,IPv6,259) check completed: NONE; no IP address configured
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3344] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:259, state:NONE)
Aug 12 18:34:24 NetworkManager[2407]: <trace> [1755020064.3344] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 1999 milliseconds (2 seconds interval)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0296] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 1000 milliseconds (1 seconds interval)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0296] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:260, periodic-check)
Aug 12 18:34:26 NetworkManager[2407]: <debug> [1755020066.0296] connectivity: (enp193s0f3u2u1,IPv4,260) skip connectivity check due to no IP address configured
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0296] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 1000 milliseconds (1 seconds interval)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0296] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:261, periodic-check)
Aug 12 18:34:26 NetworkManager[2407]: <debug> [1755020066.0296] connectivity: (enp193s0f3u2u1,IPv6,261) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:26 NetworkManager[2407]: <debug> [1755020066.0297] connectivity: (enp193s0f3u2u1,IPv4,260) check completed: NONE; no IP address configured
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0297] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:260, state:NONE)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0297] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 1999 milliseconds (2 seconds interval)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0506] connectivity: (enp193s0f3u2u1,IPv6,261) set curl resolve list to 'fedoraproject.org:80:2604:1580:fe00:0:dead:beef:cafe:fed1,2620:52:3:1:dead:beef:cafe:fed7,2600:2701:4000:5211:dead:beef:fe:fed3,2620:52:6:1121:bead:cafe:feed:fed6,2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:3:1:dead:beef:cafe:fed6,2605:bc80:3010:600:dead:beef:cafe:fed9,2620:52:6:1121:bead:cafe:feed:fed5'
Aug 12 18:34:26 NetworkManager[2407]: <debug> [1755020066.0511] connectivity: (enp193s0f3u2u1,IPv6,261) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0511] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:261, state:LIMITED)
Aug 12 18:34:26 NetworkManager[2407]: <trace> [1755020066.0511] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 1978 milliseconds (2 seconds interval)
Aug 12 18:34:26 NetworkManager[2407]: <debug> [1755020066.0511] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity state changed from NONE to LIMITED
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0291] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 2000 milliseconds (2 seconds interval)
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0292] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:262, periodic-check)
Aug 12 18:34:28 NetworkManager[2407]: <debug> [1755020068.0292] connectivity: (enp193s0f3u2u1,IPv4,262) skip connectivity check due to no IP address configured
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0292] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 2000 milliseconds (2 seconds interval)
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0293] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:263, periodic-check)
Aug 12 18:34:28 NetworkManager[2407]: <debug> [1755020068.0293] connectivity: (enp193s0f3u2u1,IPv6,263) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:28 NetworkManager[2407]: <debug> [1755020068.0294] connectivity: (enp193s0f3u2u1,IPv4,262) check completed: NONE; no IP address configured
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0294] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:262, state:NONE)
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0294] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 4000 milliseconds (4 seconds interval)
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0304] connectivity: (enp193s0f3u2u1,IPv6,263) set curl resolve list to 'fedoraproject.org:80:2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:6:1121:bead:cafe:feed:fed6,2604:1580:fe00:0:dead:beef:cafe:fed1,2620:52:3:1:dead:beef:cafe:fed7,2605:bc80:3010:600:dead:beef:cafe:fed9,2620:52:6:1121:bead:cafe:feed:fed5,2620:52:3:1:dead:beef:cafe:fed6,2600:2701:4000:5211:dead:beef:fe:fed3'
Aug 12 18:34:28 NetworkManager[2407]: <debug> [1755020068.0307] connectivity: (enp193s0f3u2u1,IPv6,263) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0307] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:263, state:LIMITED)
Aug 12 18:34:28 NetworkManager[2407]: <trace> [1755020068.0307] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 3998 milliseconds (4 seconds interval)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0298] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 3999 milliseconds (4 seconds interval)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0299] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:264, periodic-check)
Aug 12 18:34:32 NetworkManager[2407]: <debug> [1755020072.0299] connectivity: (enp193s0f3u2u1,IPv4,264) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0300] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 3999 milliseconds (4 seconds interval)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0300] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:265, periodic-check)
Aug 12 18:34:32 NetworkManager[2407]: <debug> [1755020072.0300] connectivity: (enp193s0f3u2u1,IPv6,265) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0314] connectivity: (enp193s0f3u2u1,IPv6,265) set curl resolve list to 'fedoraproject.org:80:2620:52:6:1121:bead:cafe:feed:fed5,2620:52:3:1:dead:beef:cafe:fed7,2600:2701:4000:5211:dead:beef:fe:fed3,2605:bc80:3010:600:dead:beef:cafe:fed9,2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:6:1121:bead:cafe:feed:fed6,2604:1580:fe00:0:dead:beef:cafe:fed1,2620:52:3:1:dead:beef:cafe:fed6'
Aug 12 18:34:32 NetworkManager[2407]: <debug> [1755020072.0318] connectivity: (enp193s0f3u2u1,IPv6,265) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0318] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:265, state:LIMITED)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0318] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 7997 milliseconds (8 seconds interval)
Aug 12 18:34:32 NetworkManager[2407]: <trace> [1755020072.0490] connectivity: (enp193s0f3u2u1,IPv4,264) set curl resolve list to 'fedoraproject.org:80:34.211.44.206,140.211.169.196,152.19.134.142,38.145.32.20,8.43.85.73,152.19.134.198,67.219.144.68,38.145.32.21,8.43.85.67'
Aug 12 18:34:36 NetworkManager[2407]: <trace> [1755020076.0292] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 8000 milliseconds (8 seconds interval)
Aug 12 18:34:36 NetworkManager[2407]: <trace> [1755020076.0293] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] start check (seq:266, periodic-check)
Aug 12 18:34:36 NetworkManager[2407]: <debug> [1755020076.0294] connectivity: (enp193s0f3u2u1,IPv4,266) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:36 NetworkManager[2407]: <trace> [1755020076.0307] connectivity: (enp193s0f3u2u1,IPv4,266) set curl resolve list to 'fedoraproject.org:80:18.156.194.220,185.141.165.254,38.145.32.21,35.158.105.37,38.145.32.20,3.8.95.119,85.236.55.6,152.19.134.142,152.19.134.198'
Aug 12 18:34:37 NetworkManager[2407]: <debug> [1755020077.5272] connectivity: (enp193s0f3u2u1,IPv4,264) check completed: FULL; expected response
Aug 12 18:34:37 NetworkManager[2407]: <trace> [1755020077.5273] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:264, state:FULL)
Aug 12 18:34:37 NetworkManager[2407]: <trace> [1755020077.5273] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 298502 milliseconds (300 seconds interval)
Aug 12 18:34:37 NetworkManager[2407]: <debug> [1755020077.5273] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity state changed from NONE to FULL
Aug 12 18:34:40 NetworkManager[2407]: <trace> [1755020080.0296] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 8000 milliseconds (8 seconds interval)
Aug 12 18:34:40 NetworkManager[2407]: <trace> [1755020080.0297] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:267, periodic-check)
Aug 12 18:34:40 NetworkManager[2407]: <debug> [1755020080.0298] connectivity: (enp193s0f3u2u1,IPv6,267) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:40 NetworkManager[2407]: <trace> [1755020080.0308] connectivity: (enp193s0f3u2u1,IPv6,267) set curl resolve list to 'fedoraproject.org:80:2600:2701:4000:5211:dead:beef:fe:fed3,2600:1f14:fad:5c02:5270:306c:35d6:1f81,2620:52:3:1:dead:beef:cafe:fed7,2620:52:6:1121:bead:cafe:feed:fed5,2604:1580:fe00:0:dead:beef:cafe:fed1,2620:52:6:1121:bead:cafe:feed:fed6,2605:bc80:3010:600:dead:beef:cafe:fed9,2620:52:3:1:dead:beef:cafe:fed6'
Aug 12 18:34:40 NetworkManager[2407]: <debug> [1755020080.0310] connectivity: (enp193s0f3u2u1,IPv6,267) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:34:40 NetworkManager[2407]: <trace> [1755020080.0310] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:267, state:LIMITED)
Aug 12 18:34:40 NetworkManager[2407]: <trace> [1755020080.0310] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 15998 milliseconds (16 seconds interval)
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.0302] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 15999 milliseconds (16 seconds interval)
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.0304] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] start check (seq:268, periodic-check)
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.0305] connectivity: (enp193s0f3u2u1,IPv6,268) start request to 'http://fedoraproject.org/static/hotspot.txt' (try resolving 'fedoraproject.org' using systemd-resolved)
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.0498] connectivity: (enp193s0f3u2u1,IPv6,268) set curl resolve list to 'fedoraproject.org:80:2a05:d014:10:7803:e679:200f:1d55:a3d,2a05:d01c:c6a:cc01:80a4:89a8:76d0:aa54,2600:2701:4000:5211:dead:beef:fe:fed3,2605:bc80:3010:600:dead:beef:cafe:fed9,2a05:d014:10:7803:142c:f27e:9113:eb70,2001:4178:2:1269::fed2,2604:1580:fe00:0:dead:beef:cafe:fed1'
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.0502] connectivity: (enp193s0f3u2u1,IPv6,268) check completed: LIMITED; check failed: (7) Could not connect to server
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.0502] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] complete check (seq:268, state:LIMITED)
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.0503] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv6] periodic-check: re-scheduled in 31979 milliseconds (32 seconds interval)
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.3279] connectivity: (enp193s0f3u2u1,IPv4,266) check completed: LIMITED; timeout
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.3280] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] complete check (seq:266, state:LIMITED)
Aug 12 18:34:56 NetworkManager[2407]: <trace> [1755020096.3280] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity: [IPv4] periodic-check: re-scheduled in 0 milliseconds (1 secondsinterval)
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.3281] device[c9af564b3ddfa087] (enp193s0f3u2u1): connectivity state changed from FULL to LIMITED
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.3282] manager: connectivity checking indicates LIMITED
Aug 12 18:34:56 NetworkManager[2407]: <debug> [1755020096.3283] dispatcher: (38) dispatching action 'connectivity-change'

Regarding nmcli general logging level TRACE domains ALL, do I need to execute a command to revert the logging preference, or does it reset upon reboot? I presume that having it enabled drains charge noteworthily more than having it disabled would.

14

Log #1, IPv4 Wi-Fi

This looks fine.

Log #1, IPv4 Ethernet

Missing IPv4 default route on the wire looks like a misconfiguration or the result of using another conflicting network appliance that messes your routes or routing rules.
There’s not enough data to make any conclusion, but each wired and wireless interface should have its own IPv4 default route with smaller metric on the wire, see:

ip -4 route show default table all
ip -4 route get 1 dev enp193s0f3u2u1
ip -4 route get 1

Also some VPNs implement a kill switch that results in similar behavior.

Log #1 + Log #2, IPv6 Wi-Fi + IPv6 Ethernet

The router should not announce IPv6 default route without IPv6 connectivity.
Possible solutions:

  • Provide IPv6 connectivity on the router with IPv6 tunnel broker, Cloudflare WARP, Tor, etc.
  • Stop the router from announcing IPv6 default route, possibly by utilizing an IPv6 ULA prefix, or using only IPv6 LLA and disabling IPv6 PD.
  • Ignore IPv6 default route on the client:
nmcli connection modify WIFI_CONNECTION ipv6.never-default yes
nmcli connection modify ETH_CONNECTION ipv6.never-default yes

Log #2, IPv4 Ethernet

This looks normal at first, but then it timeouts for no apparent reason, which may be related to rate limiting, or L1/L2 connectivity issues, or missing DNS reply on the latest A query, etc.
There’s not enough data to make any conclusion without at least understanding if this behavior is reproducible and what happens next.

1 Like
15

@vgaetera, my apologies for not responding! I somehow accidentally triaged the e-mail notifying me of this as complete without actually reading it.

Although the previous reproduction steps:

…don’t appear to be reproducing now, on my FW16, with:

VERSION_ID=42
VARIANT="KDE Plasma Desktop Edition"

…I’ll respond with what you ask (on my FW16):

  1. I want to provide you with a map of the network, but I’ve not had much luck:

    1278×797 58.3 KB
    [1]

    Though, considering how much of a novice I am at this, that’s likely because I’m unfamiliar with what nmap command to utilise (the default isn’t very useful).

      1. #!/usr/bin/env sh
ip -4 route show default table all

      2. default via 192.168.1.1 dev wlp1s0 proto dhcp src 192.168.1.219 metric 600

      1. #!/usr/bin/env sh
ip -4 route get 1 dev enp193s0f3u2u1

      2. 1.0.0.0 dev enp193s0f3u2u1 src 192.168.1.219 uid 1000 
    cache 

      1. #!/usr/bin/env sh
ip -4 route get 1

      2. 1.0.0.0 via 192.168.1.1 dev wlp1s0 src 192.168.1.219 uid 1000 
    cache

  3. Solely flathub.org/apps/com.protonvpn.www is installed:

              ID: com.protonvpn.www
         Ref: app/com.protonvpn.www/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 4.9.7
     License: GPL-3.0
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 62.7 MB
     Runtime: org.gnome.Platform/x86_64/47
         Sdk: org.gnome.Sdk/x86_64/47

      Commit: 199c282fd41539e3396f6fddce53558dde558f5a130f0457c0d90857a70fbd95
      Parent: 234263367e9d7434d29e18919ea917b73bcef50a0f56d46953f98f1b11ef485f
     Subject: Merge pull request #394 from flathub/update-master-c6efe0c (8582be9e299a)
        Date: 2025-07-14 08:01:04 +0000

    …and its kill-switch should be disabled:

    Screenshot_20251009_163839
    Screenshot_20251009_1638391278×494 58 KB

    I don’t know how to provide more deterministic confirmation.

About all else, because this does not appear to reproduce anymore, despite my LAN gateway still having its InterNet-inaccessible-but-LAN-accessible IPv6 enabled, I’ll mark this comment as the “solution”. If anyone else, with the latest package selection on F42, continues to reproduce this, please attempt what @vgaetera has recommended, and inform us whether it remediates it for you.

  1. superuser.com/revisions/1926422/1 ↩︎

1 Like