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 589092 - doesn't watch for default route changes and alter the UI
doesn't watch for default route changes and alter the UI
Status: RESOLVED DUPLICATE of bug 682872
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
0.7.x
Other All
: Normal minor
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-07-20 08:21 UTC by Paul Wise
Modified: 2013-05-11 09:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Wise 2009-07-20 08:21:38 UTC
Please describe the problem:
When I change the default route manually on the command-line, NetworkManager doesn't notice this and change the UI accordingly. I change the default route manually because NM chooses the wrong one:

http://bugzilla.gnome.org/show_bug.cgi?id=589040

Before I change the default route from wired to wireless, NM shows the wired connection and afterwards it does the same. NM should listen to the kernel's (Linux/etc) network events, notice when things change and update the UI accordingly. NM should work well with the rest of the stack, notice when things are changing and accept that it is part of a larger ecosystem and that user requirements are varied.

The architecture of netconf allows this, you might want to re-architect to match that a bit closer:

http://netconf.alioth.debian.org/

Steps to reproduce:
1. Connect to wireless
2. Plugin a network cable
3. Switch the default route manually
4. Notice NM doesn't listen to Linux kernel network events (ip monitor)

Actual results:
Status icon stays as the wired icon

Expected results:
Status icon switches to wireless icon

Does this happen every time?
Yes

Other information:
Debian squeeze with NM 0.7.1
Comment 1 Pavel Simerda 2012-07-25 18:41:22 UTC
NM currently doesn't pay attention to the manual changes of the default gateway. It definitely should do it and at least log the changes.

Whether the GUI and CLI tools should reflect the manually set default route is another question.
Comment 2 Pavel Simerda 2013-05-09 11:39:20 UTC
(In reply to comment #1)
> NM currently doesn't pay attention to the manual changes of the default
> gateway. It definitely should do it and at least log the changes.

This part is already done by nm-platform in the master branch.(In reply to 

> Whether the GUI and CLI tools should reflect the manually set default route is
> another question.

GUI/CLI can only reasonably reflect this if we publish the the IP configuration for the devices.
Comment 3 Pavel Simerda 2013-05-11 09:07:28 UTC
Consolidating...

*** This bug has been marked as a duplicate of bug 682872 ***