[Bug 41148] better handling of connectivity changes: make CMs use GNetworkMonitor and/or netlink

[bugzilla-daemon at freedesktop.org]

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

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---
            Summary|NM: better handling of      |better handling of
                   |connectivity changes        |connectivity changes: make
                   |                            |CMs use GNetworkMonitor
                   |                            |and/or netlink
          Component|mission-control             |general

--- Comment #6 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Reopening and assigning to 'general' since the suggested implementation
involves CMs directly. If/when someone works on this, I suggest using this as a
metabug for CM-specific bugs against Gabble, Salut, Rakia and Idle - Haze
probably has to be WONTFIX since we don't have sufficiently fine control over
its networking.

> You can determine the source (local) IP address used by a socket with
> g_socket_get_local_address(), and you can monitor which IP addresses the
> system currently has with netlink's RTM_NEWADDR, RTM_DELADDR, RTM_GETADDR
> messages. So, combining the two, the CM could forcibly close its socket after
> the socket's source IP is lost.
...
> Rather than forcibly closing the socket immediately, it could send a ping
> with a relatively short timeout.

This Netlink monitoring could maybe go in telepathy-glib, but would be better
in GIO.

> On XMPP, XEP-0198 is one answer

That's Bug #46700.

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