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 701609 - gnetworkmonitornetlink: handle default route via device
gnetworkmonitornetlink: handle default route via device
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
: 704610 (view as bug list)
Depends on:
Blocks: 703515
 
 
Reported: 2013-06-04 22:19 UTC by Dan Winship
Modified: 2013-08-01 15:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gnetworkmonitornetlink: handle default route via device (3.14 KB, patch)
2013-06-04 22:19 UTC, Dan Winship 		committed Details | Review

Description Dan Winship 2013-06-04 22:19:35 UTC 
If the default route is via a device rather than a particular IP
address, then neither RTA_DST nor RTA_GATEWAY will be present in the
RTM_NEWROUTE message, and so GNetworkMonitorNetlink would ignore it,
and then think there was no default route. (This could happen with
certain kinds of VPNs, if they were set to route all traffic through
the VPN.)

Fix this by recognizing routes that specify RTA_OIF ("output
interface") instead of RTA_GATEWAY.
Comment 1 Dan Winship 2013-06-04 22:19:38 UTC 
Created attachment 246031 [details] [review]
gnetworkmonitornetlink: handle default route via device
Comment 2 Dan Winship 2013-06-04 22:20:36 UTC 
Pavel, can you sanity-check this?
Comment 3 Jan-Michael Brummer 2013-06-08 16:03:23 UTC 
I've patched my glib with this patch and now gnetworkmonitor reports connected when I'm connected to the office vpn. Thanks.
Comment 4 Dan Winship 2013-07-12 16:00:16 UTC 
Attachment 246031 [details] pushed as c08ef6c - gnetworkmonitornetlink: handle default route via device
Comment 5 Jonh Wendell 2013-07-20 15:56:32 UTC 
*** Bug 704610 has been marked as a duplicate of this bug. ***
Comment 6 Jonh Wendell 2013-07-20 15:57:49 UTC 
Hi, can this be backported to 2.36? so we can make gnome 3.8 a bit happier :)
Comment 7 David Woodhouse 2013-08-01 15:54:18 UTC 
Now backported.