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.
Description of problem:
iproute has removed some items from file rt_dsfield. Commands, which uses these items, have stopped to work.
--- rt_dsfield-3.10.0-87.el7 2017-08-10 11:36:22.656933568 +0200
+++ rt_dsfield-4.11.0-1.el7a 2017-08-10 11:35:42.768235784 +0200
@@ -1,17 +1,6 @@
-0x00 default
-0x10 lowdelay
-0x08 throughput
-0x04 reliability
-# This value overlap with ECT, do not use it!
-0x02 mincost
-# These values seems do not want to die, Cisco likes them by a strange reason.
-0x20 priority
-0x40 immediate
-0x60 flash
-0x80 flash-override
-0xa0 critical
-0xc0 internet
-0xe0 network
+# Differentiated field values
+# These include the DSCP and unused bits
+0x0 default
# Newer RFC2597 values
0x28 AF11
0x30 AF12
@@ -25,3 +14,13 @@
0x88 AF41
0x90 AF42
0x98 AF43
+# Older values RFC2474
+0x20 CS1
+0x40 CS2
+0x60 CS3
+0x80 CS4
+0xA0 CS5
+0xC0 CS6
+0xE0 CS7
+# RFC 2598
+0xB8 EF
Version-Release number of selected component (if applicable):
iproute-4.11.0-1.el7a
How reproducible:
100%
Steps to Reproduce:
# rpm -q iproute
iproute-3.10.0-87.el7.aarch64
# ip rule add from 192.168.1.0/24 tos lowdelay
# ip rule list
0: from all lookup local
32765: from 192.168.1.0/24 tos lowdelay lookup main
32766: from all lookup main
32767: from all lookup default
# ip rule list | grep lowdelay
32765: from 192.168.1.0/24 tos lowdelay lookup main
# rpm -q iproute
iproute-4.11.0-1.el7a.ppc64le
# ip rule add from 192.168.1.0/24 tos lowdelay
Error: argument "lowdelay" is wrong: TOS value is invalid
# ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
# ip rule list | grep lowdelay
<<nothing>>
This upstream change was intentional:
commit eb5d01ff38080935a1a528e4c99cab42bf93d762
Author: Stephen Hemminger <stephen>
Date: Sun Sep 14 20:40:37 2014 -0700
update dsfield file values
Update the rt_dsfield file to contain values defined in current RFC.
The days of TOS precedence are gone, even Cisco doesn't refer
to these in the documents.
Do you think we should stay compatible? I guess it shouldn't be a problem to ship a customized rt_dsfield config file.
(In reply to Jaroslav Aster from comment #2)
> Hi Phil,
>
> yes, I think it would be better to stay compatible with older version.
OK, then let's do this.
Thanks, Phil
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://access.redhat.com/errata/RHEA-2017:3172