From: Phil Sutter <phil@nwl.cc>
To: Anssi Hannula <anssi.hannula@bitwise.fi>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
Hiroaki SHIMODA <shimoda.hiroaki@gmail.com>
Subject: Re: [PATCH iproute2] man: tc-u32: Fix page to match new firstfrag behavior
Date: Thu, 4 Nov 2021 17:06:45 +0100 [thread overview]
Message-ID: <20211104160645.GR1668@orbyte.nwl.cc> (raw)
In-Reply-To: <20211104144203.3581611-1-anssi.hannula@bitwise.fi>
On Thu, Nov 04, 2021 at 04:42:05PM +0200, Anssi Hannula wrote:
> Commit 690b11f4a6b8 ("tc: u32: Fix firstfrag filter.") applied in 2012
> changed the "ip firstfrag" selector to not match non-fragmented packets
> anymore.
>
> However, the documentation added in f15a23966fff ("tc: add a man page
> for u32 filter") in 2015 includes an example that relies on the previous
> behavior (non-fragmented packet counted as first fragment).
>
> Due to this, the example does not work correctly and does not actually
> classify regular SSH packets.
>
> Modify the example to use a raw u16 selector on the fragment offset to
> make it work, and also make the firstfrag description more clear about
> the current behavior.
>
> Fixes: f15a23966fff ("tc: add a man page for u32 filter")
> Signed-off-by: Anssi Hannula <anssi.hannula@bitwise.fi>
> Cc: Phil Sutter <phil@nwl.cc>
> Cc: Hiroaki SHIMODA <shimoda.hiroaki@gmail.com>
Acked-by: Phil Sutter <phil@nwl.cc>
> I suspect the original behavior was intentional, but the new one has
> been out for 9 years now so I guess it is too late to change again.
At least it seems nobody really depends on the old behaviour (or doesn't
update iproute2 then). :)
Thanks, Phil
prev parent reply other threads:[~2021-11-04 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 14:42 [PATCH iproute2] man: tc-u32: Fix page to match new firstfrag behavior Anssi Hannula
2021-11-04 16:06 ` Phil Sutter [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=20211104160645.GR1668@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=anssi.hannula@bitwise.fi \
--cc=netdev@vger.kernel.org \
--cc=shimoda.hiroaki@gmail.com \
--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 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).