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:

ip rule command allows to remove rule with priority 0, but manpage ip-rule says that it is not possible.

Rule 0 is special. It cannot be deleted or overridden.


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

iproute-3.10.0-21.el7


How reproducible:

Always.


Steps to Reproduce:

# ip rule show
0:      from all lookup local 
32766:  from all lookup main 
32767:  from all lookup default 

# ip rule del prio 0

# ip rule show
32766:  from all lookup main 
32767:  from all lookup default 


Actual results:

Rule with prio 0 can be removed.


Expected results:

Rule with prio 0 cannot be removed or manpage ip-rule has to be changed.


Additional info:

This apparently applies to upstream manpage as well.

We're going to talk to upstream and have this fixed in one way or another there first.

I believe it is up to the kernel to decide whether a rule can be removed or not. Maybe it was misdocumented from the begining, maybe there was a change in the kernel. I would personally just remove the line.

Posted upstream as part of a larger documentation patch.

http://marc.info/?l=linux-netdev&m=142893422717620&w=2

Hi Pavel,

I tested it on rhel6 and there is not possible to remove rule with prio 0.

# rpm -q iproute
iproute-2.6.32-45.el6.x86_64

# uname -r
2.6.32-504.el6.x86_64

# ip rule del prio 0
RTNETLINK answers: Operation not permitted

So there is true that rule with prio 0 is special.

I agree that it is a documentation issue.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2117.html