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.

Description of problem:

in my /etc/sysconfig/network-scripts I traditionally have
in route-ethx:
table my_table default via an.IP
table my_table to a.Net dev ethX
etc
and in rule-ethX:
from a.Net table my_table

NM does not use those, I could not confirm this in any docs files thus question mark - is this a bug?
And if not then what is NM's way of achieving/allowing such a common scenario? 

Version-Release number of selected component (if applicable):

NetworkManager-glib-0.9.9.1-28.git20140326.4dba720.el7_0.2.x86_64
NetworkManager-0.9.9.1-28.git20140326.4dba720.el7_0.2.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This is not supported (yet).

NM only handles route from the main table. Hence this configuration is ignored.

Would be great to extend NM to support this, but no concrete plan for it yet.


An acceptable(?) workaround could be to add a dispatcher script that adds the routes/rules. See `man NetworkManager`.

yes dispatched I used in the end, and YES! it would be great to have NM account for this, NM is cute tool but here misses one bit which old network scripts cover nicely.

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