From: Pavel Balaev <mail@void.so>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2] ipv4: make DSCP values works with ip rules
Date: Tue, 20 Nov 2018 17:36:25 +0300 [thread overview]
Message-ID: <20181120143624.GA6920@rnd.infotecs.ru> (raw)
In-Reply-To: <20181120141218.GA3474@bistromath.localdomain>
On Tue, Nov 20, 2018 at 03:12:18PM +0100, Sabrina Dubroca wrote:
> Hi Pavel,
>
> 2018-11-20, 16:29:36 +0300, Pavel Balaev wrote:
> > This patch adds ability to set DSCP values in ip rules.
>
> You dropped the RFC reference that you had in v1.
>
RFC2474 and RFC2597 values.
> > Values presented in /etc/iproute3/rt_dsfield and now can be used in rules.
>
> iproute3?
>
That was a typo, iproute2.
> >
> > Example:
> > $ ip ru add from 10.88.0.2 tos AF23 lookup dscp.
> > Result:
> > ---
>
> Be careful when you write commit messages. "git am" is going to cut
> out everything that comes after the first ^---$ line it sees, so the
> rest of those explanations, as well as your sign-off, will be dropped.
>
> > 32762: from 10.88.0.2 tos AF43 lookup dscp
> > ---
> >
> > Patch was tested with such configuration:
> >
> > +-----------+
> > | 10.88.0.2 | -> ping 172.16.0.1 -Q 0x58 ->
> > | host0 |
> > +-----------+
> >
> > +-------------------------------------+
> > | router with patched kernel |
> > | |
> > -> | from 10.88.0.2 tos AF43 lookup dscp |->
> > | table dscp: |
> > | 172.16.0.0/24 via 10.200.0.2 |
> > +-------------------------------------+
> >
> > +------------------+
> > -> | eth0: 10.200.0.2 |
> > | eth1: 172.16.0.1 |
> > | host1 |
> > +------------------+
> >
> > Signed-off-by: Pavel Balaev <mail@void.so>
>
> --
> Sabrina
Ok. Got it. Tnx.
prev parent reply other threads:[~2018-11-21 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 13:29 [PATCH v2] ipv4: make DSCP values works with ip rules Pavel Balaev
2018-11-20 14:12 ` Sabrina Dubroca
2018-11-20 14:36 ` Pavel Balaev [this message]
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=20181120143624.GA6920@rnd.infotecs.ru \
--to=mail@void.so \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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