Comment 218 for bug 191889

Revision history for this message
Henry Wertz (hwertz) wrote : Re: [MASTER] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager.

     I've found a kludgy "fix" for this (that doesn't just involve removing nm, since it's wireless and wired handling are nice). In my case, I have a Inspiron 2200 with wifi set via ndiswrapper (which works fine) and an aircard (Verizon PC5740) which worked except for the "Offline mode" problem. So it's the case where if I don't have wifi, and dial via CDMA, I get the "Work Offline" stuff going on.

     So, if I go into /etc/dbus-1/system.d/NetworkManager.conf, I inserted in line 18 (all on one line):
<deny send_interface="org.freedesktop.NetworkManager" send_member="state"/>

     (That's in the 'policy at_console="true" ' section of the file in case yours is arranged a little differently for whatever reason.)

     This file seems to be checked on-the-fly, I could change this and see an immediate effect on firefox (although I rebooted to check for side effects).

     Consequences:
     This blocks firefox and any other app's attempt to get the online/offline state from NetworkManager, which makes it (and probably any other apps that try to check NetworkManager) decide Networkmanager is not there and assume online state. It ALSO blocks nm-applets access to this though...
     Since nm-applet can't get the online/offline state from NetworkManager either, it doesn't show online state properly (it'll show the exclamation mark while the network is up and running fine for static IP wifi and ethernet)... For regular ol' DHCP wifi, it does still show the signal bars (since blocking "status" doesn't block wifi signal strength info).
     Also, under "manual configuration" the "Roaming mode" text changes to "This network interface is not configured", and the checked "Roaming mode" checkboxes change to uncheckd "Enable this connection" checkboxes. But the interface seems consistent and to behave itself. Problem solved as far as I'm concerned, until I got to NetworkManager 0.7!