After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778688 - o.fd.NetworkManager:Connectivity == 4 with all network interfaces turned off
o.fd.NetworkManager:Connectivity == 4 with all network interfaces turned off
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-02-15 15:37 UTC by Debarshi Ray
Modified: 2020-11-12 14:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
NetworkManager logs (46.81 KB, text/x-log)
2017-02-15 15:37 UTC, Debarshi Ray
Details
Test program using the GNetworkMonitor AP (2.46 KB, text/x-csrc)
2017-03-01 12:30 UTC, Debarshi Ray
Details

Description Debarshi Ray 2017-02-15 15:37:55 UTC
Created attachment 345843 [details]
NetworkManager logs

The value of o.fd.NetworkManager:Connectivity on /o/fd/NetworkManager doesn't change even if I turn off both my WiFi and Ethernet interfaces. It stays at 4.

This is on Fedora 24 and 25 with the following versions:
NetworkManager-1.2.6-1.fc24.x86_64
NetworkManager-1.4.4-3.fc25.x86_64

I have been told that it works (again) with 1.6.0, but I haven't been able to test.
Comment 2 Debarshi Ray 2017-03-01 11:39:57 UTC
Given that this worked in the past (eg., Fedora 21 with 0.9.10.2) and allegedly works in 1.6.x, could it be backported to 1.4.x and 1.2.x.? Those are the versions that Fedora 25 and 24 are using. It seems we already have a backport in RHEL/CentOS 7 because it has 1.4.x, but doesn't exhibit this bug.
Comment 3 Debarshi Ray 2017-03-01 12:11:41 UTC
Or it could be that it worked on my Fedora 21 and CentOS 7 VMs because they don't have the virbr0 bridge set up by libvirt, which I have on my bare metal Fedora 24 and 25 laptops.

With both the WiFi and Ethernet interfaces switched off, I have:

[rishi@kolache ~]$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
[rishi@kolache ~]$
Comment 4 Debarshi Ray 2017-03-01 12:30:29 UTC
Created attachment 346965 [details]
Test program using the GNetworkMonitor AP

Regardless of the details further down the stack, here is a test program using GIO's GNetworkMonitor API [1] that demonstrates the bug. GNetworkMonitor is an interface which has a NetworkManager backed implementation for systems which use NM. This is the API a lot of GNOME components use to monitor network connectivity.

On disconnecting from the network, the value of the GNetworkMonitor:network-available property continues to be TRUE. However, GNetworkMonitor::network-changed is emitted with available=FALSE.

[1] https://developer.gnome.org/gio/stable/GNetworkMonitor.html
Comment 5 André Klapper 2020-11-12 14:31:10 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).