From: Daniel Lakeland <dlakelan@street-artists.org>
To: Stephen Hemminger <stephen@networkplumber.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:33:48 -0800 [thread overview]
Message-ID: <099CD994-080F-43A8-9D50-A6947208908C@street-artists.org> (raw)
In-Reply-To: <20171213101259.65652da6@xeon-e3>
On December 13, 2017 10:12:59 AM PST, Stephen Hemminger <stephen@networkplumber.org> wrote:
>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.
>
I figure it's still biting me because no one reported it. This is with modern Debian testing system.
>
>The kernel is complaining that ip rule is not valid, (ie not iproute2
>issue).
Note that like some of those other people I was able to get ip rule to accept tos values with just low order bits set... On my phone now so can't test an example but it was a tos like 0x0c or something.
I'm really not familiar with internals or who's in charge of what I just wanted to be sure this issue hit some kernel netdev people's radar instead of dropping on the floor!!
>Not sure exactly why or where in fib_rules.c this is happening.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-12-13 18:33 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
2017-12-13 18:33 ` Daniel Lakeland [this message]
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=099CD994-080F-43A8-9D50-A6947208908C@street-artists.org \
--to=dlakelan@street-artists.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.