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 722843 - NM should treat routes differently depending on their origin
NM should treat routes differently depending on their origin
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-01-23 16:48 UTC by Thomas Haller
Modified: 2014-01-24 17:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas Haller 2014-01-23 16:48:25 UTC
This is upstream bug for https://bugzilla.redhat.com/show_bug.cgi?id=1005416:

To quote rhbz#1005416

This is a bug for tracking the implementation of a new functionality in NetworkManager.


Currently, NM treads all routes the same, regardless how they were configured.
Routes should be tagged internally in NM depending on their origin (e.g. DHCP, RA, static, ...).


One use of this is for example in bug #999544. Currently NM considers the activation of a connection as failed, when a route cannot be set. This makes mostly sense for manually configured routes, because a partial failure of setting a route cannot be displayed to clients. This behaviour might be undesired for routes from DHCP because a wrong configured route on the DHCP server could make the connection unusable.




Note also the related discussion in bug https://bugzilla.gnome.org/show_bug.cgi?id=721771#c20

Note also, that this is currently be implemented as part of bug 721724, see branch dcbw/vpn-no-iface
Comment 1 Dan Williams 2014-01-24 17:57:58 UTC
dcbw/vpn-no-iface merged to master along with your fix for this bug.