From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Lakeland <dlakelan@street-artists.org>
Cc: netdev@vger.kernel.org
Subject: Re: BUG REPORT: iproute2 seems to have bug with dsfield/tos in ip-rule and ip-route
Date: Wed, 13 Dec 2017 10:12:59 -0800 [thread overview]
Message-ID: <20171213101259.65652da6@xeon-e3> (raw)
In-Reply-To: <9e606c3b-915c-2608-c8aa-aa3167f51f8d@street-artists.org>
On Wed, 13 Dec 2017 09:40:08 -0800
Daniel Lakeland <dlakelan@street-artists.org> wrote:
> This same problem as detailed here
>
> http://lists.openwall.net/netdev/2010/03/26/36
This mail reports an issue from 7 years ago, much nas
changed since then.
>
> or here:
>
> https://www.spinics.net/lists/lartc/msg22541.html
>
> bit me today
>
> I tried either
>
> ip rule add dsfield CS6 table 100
>
> or
>
> ip rule add dsfield 0xc0 table 100
>
> or replace dsfield with tos, all return:
>
> RTNETLINK answers: Invalid argument
>
> on the other hand, for ip route it will accept the ds/tos values
>
> ip route add default dsfield CS6 dev dummy0
>
> or
>
> ip route add default dsfield 0xc0 dev dummy0
>
> but packets tagged with CS6 don't go to dummy0 they go the regular
> default route
>
>
The kernel is complaining that ip rule is not valid, (ie not iproute2 issue).
Not sure exactly why or where in fib_rules.c this is happening.
next prev parent reply other threads:[~2017-12-13 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 17:40 BUG REPORT: iproute2 seems to have bug with dsfield/tos in ip-rule and ip-route Daniel Lakeland
2017-12-13 18:12 ` Stephen Hemminger [this message]
2017-12-13 18:33 ` Daniel Lakeland
2017-12-13 19:05 ` Daniel Lakeland
2017-12-13 22:40 ` David Ahern
2017-12-13 22:52 ` Daniel Lakeland
2017-12-13 23:05 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171213101259.65652da6@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dlakelan@street-artists.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).