I constantly see "Limited Connectivity" notifications

Help
,
1

Every few minutes, I see:

332×117 12.1 KB

I’ve not noticed packet loss. I’m able to connect to the internet. This has been occurring irregularly across different residences, broadband connections, and computer systems, for approximately 2 years.

2

Not really a Plasma issue - but generally you should try restarting networkmanager ‘systemctl restart Networkmanager’ - something like ❯ systemctl restart NetworkManager.service

You can also completely delete the current connection profile and reconnect.

Next up, look into your DNS Settings - check your router and verify it from other devices.

Connecting to an alternative network might also give some insight (e.g. disconnect from your normal connection, and connect to a phone hotspot).

Finally, you can disable the connectivity checking, look at any firewall or proxy settings you have,

IPv6 can also cause false warnings - you can try ignoring that.

This message appears when Plasma checks connectivity by pinging a server, and the ping fails even if HTTP/HTTPS works.

Some networks can also block ping requests.

2 Likes
3

I have seen this a while back (maybe 1-2 weeks ago) but not every few minutes, maybe 4-5 times a day.

My assumption back then was that the system occasionally checks availability of a specific server and that server might have had issues

2 Likes
4

@krake, that’s my estimation too, hence why I mentioned it here. I don’t believe that I see it when booted into Windows 11 24H2.

I should have been more specific. It occurs ⪅ every 20 mins.

@ben2talk, am I correct that a reboot is equivalent? I can’t imagine the service persists across reboots, when even the initialisation service itself is inoperative.

I’ll try your suggestions:

  1. Disabling Wi-Fi whilst retaining Ethernet.
  2. The opposite.
  3. Utilise a different device.
  4. Utilise a cellular network (extended via a smartphone, acting as an AP).

Uniquely, my gateway, despite being provided by my ISP, and despite including IPv6-capable firmware, isn’t actually capable of negotiating an IPv6 connection with the ISP. I was informed of this by my ISP. Might that be the cause, then?

1 Like
5

I’m sorry - I’m generally pretty dumb figuring out network issues, I find many avenues but my troubleshooting is mostly down to trial and error.

I wish you luck.

Regards.

1 Like
6

This doesn’t appear to reproduce with solely Ethernet enabled. Previously, I had Wi-Fi and Ethernet enabled, which would explain the Ethernet symbol in the notification.