Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAntoni Segura Puimedon
2014-05-06 09:47:34 UTC
Description of problem:
When asking iproute about tables that need upward of 31 bits to be represented, it will not give the expected output of just the routing entries of that table.
Version-Release number of selected component (if applicable):
iproute-2.6.32-31.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. ip route add default via 10.34.60.33 table 2147483648
2. ip route add default via 10.34.60.34 table 2147483649
3. ip route add default via 10.34.60.35 table 214
4. ip route table show table 2147483648
Actual results:
default via 10.34.60.35 dev eth1
default via 10.34.60.33 dev eth1
10.34.60.0/22 dev eth1 proto kernel scope link src 10.34.60.244
169.254.0.0/16 dev eth1 scope link metric 1002
default via 10.34.63.254 dev eth1
default via 10.34.60.34 dev eth1
default via 10.34.60.33 dev eth1
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.34.60.0 dev eth1 proto kernel scope link src 10.34.60.244
broadcast 10.34.63.255 dev eth1 proto kernel scope link src 10.34.60.244
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
local 10.34.60.244 dev eth1 proto kernel scope host src 10.34.60.244
local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1
Expected results:
default via 10.34.60.33 dev eth1
Additional info:
This is an expected behavior.
The table ID can be anywhere between 1 and 2^31; any other value is invalid and the `local' table is returned instead.
However, I see the manpage included in el6 only mentions the historical limit of 1-255. This should be updated. However, that's a different issue.
Comment 3Antoni Segura Puimedon
2014-05-06 14:21:47 UTC
How is this expected behavior when it works just fine with newer iproute2 (as in fedora 20).
~/c/vdsm ❯❯❯ sudo ip route add default via 192.168.1.2 table 2147483648
~/c/vdsm ❯❯❯ sudo ip route show table 2147483648
default via 192.168.1.2 dev wlp3s0
~/c/vdsm ❯❯❯
In the kernel, in net/ipv4/route.c I can see how the value put for rta_table
is put with NLA_PUT_U32 and in fact putting it and retrieving it shows the
correct values for 2147483648, so it seems as if there is a bug in iproute.
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-2016-0895.html