[Bug 56635] make NM/ConnMan integration into plugins or use GNetworkMonitor?

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Apr 30 18:45:40 CEST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=56635

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Created attachment 78658
  --> https://bugs.freedesktop.org/attachment.cgi?id=78658&action=edit
Replace ConnMan connectivity support with  GNetworkMonitor

The information we're getting from ConnMan is no more informative
than GNetworkMonitor, and a ConnMan GNetworkMonitor implementation
exists (e.g. <https://github.com/jukkar/connman-network-monitor>),
so we might as well go via that.

On NetworkManager systems, we now use NetworkManager to detect
transient states like DISCONNECTING, but use the GNetworkMonitor
to detect whether the interface is up. If NetworkManager is the only
thing managing an interface, that makes no difference, but if there is
an interface not managed by NetworkManager, the default netlink
GNetworkMonitor will say we're online even while NM is DISCONNECTED,
which is what we want.

On non-NetworkManager, non-ConnMan systems where netlink works,
netlink will tell us at least the basics of what's going on, and we
can avoid trying to connect while there is no Internet route.

On systems without a working GNetworkMonitor, GIO's default
implementation will say "yes, you are online" at all times, which is
no worse than we had previously.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.



More information about the telepathy-bugs mailing list