RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

vpn-no-iface was merged along with your fix for better handling of externally-sourced routes.

reproducer:
setting 192.169.0.128/24 192.168.0.1 with routes to 192.168.0.22 fails localy, 

but after starting dnsmasq with:
interface=enp0s25
dhcp-range=enp0s25,192.169.0.222,192.169.0.229,4h
dhcp-option=121,10.0.0.0/24,192.168.0.22

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[941]: <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.