Incorrectly reporting limited connectivity while using VPN application (Mullvad)
It seems that under certain circumstances when connected to Mullvad VPN using their app, NetworkManager incorrectly reports connectivity as being "limited" despite actually having full Internet connectivity. This might be specific to what the Mullvad app in particular does in the background.
Here's the original bug from the Mullvad issue tracker, with a comment suggesting this should be reported upstream.
When networking in NetworkManager is initially disabled and then enabled while Mullvad is connected, the problem consistently appears. It also seems to appear when Mullvad is connected while NetworkManager is already active but seems to take some time before NetworkManager reports limited connectivity.
Despite reporting "limited connectivity", there's actually full Internet connectivity.
$ NetworkManager --version
1.20.12-1.fc31
$ mullvad version
Current version: 2020.5
Is supported: true
Is up to date: true
Latest version: 2020.5
$ mullvad connect
$ mullvad status
Tunnel status: Connected to WireGuard - 87.101.92.154:42225 over UDP
$ nmcli networking connectivity
full
$ nmcli networking off
$ nmcli networking on
$ nmcli general
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (site only) limited enabled enabled enabled enabled
$ ping freedesktop.org -c 2
PING freedesktop.org (131.252.210.176) 56(84) bytes of data.
64 bytes from annarchy.freedesktop.org (131.252.210.176): icmp_seq=1 ttl=44 time=82.8 ms
64 bytes from annarchy.freedesktop.org (131.252.210.176): icmp_seq=2 ttl=44 time=83.7 ms
--- freedesktop.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 82.815/83.246/83.677/0.431 ms
I've attached the NetworkManager system logs while running the above commands (with log level=TRACE and domains=ALL). Let me know if any more info is required!