Red Hat Bugzilla – Bug 1005416
NM should treat routes differently depending on their origin
Last modified: 2014-06-17 22:48:31 EDT
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.
Over to you thomas; I'll try to merge dcbw/vpn-no-iface this week to provide the basis for your work here. Thanks!
A related discussion to this topic took place at https://bugzilla.gnome.org/show_bug.cgi?id=721771#c20 and following
Created upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=722843
vpn-no-iface was merged along with your fix for better handling of externally-sourced routes.
setting 18.104.22.168/24 192.168.0.1 with routes to 192.168.0.22 fails localy,
but after starting dnsmasq with:
and connecting from other box I was able co get address and activate connection correctly.
there was a message about failing routes:
Apr 28 12:45:29 dhcp131-232 NetworkManager: <error> [1398681929.384658] [platform/nm-linux-platform.c:1366] add_object(): Netlink error adding 10.0.0.0/24 via 192.168.0.22 dev enp0s25 metric 1 mss 0 src unknown: Unspecific failure
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.