From: Matthieu Baerts <matttbe@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>,
netfilter-devel@vger.kernel.org
Cc: coreteam@netfilter.org
Subject: Re: [PATCH nft] doc: add MPTCP subtypes documentation to man page
Date: Wed, 30 Sep 2026 20:38:49 +0200 [thread overview]
Message-ID: <ef8c754d-616f-489f-b556-073efa491cd2@kernel.org> (raw)
In-Reply-To: <20260929141425.4852-1-fmancera@suse.de>
Hi Fernando,
On 29/09/2026 16:14, Fernando Fernandez Mancera wrote:
> In addition, document the limitation when there are multiple MPTCP
> options.
Thank you for this patch!
> diff --git a/doc/payload-expression.txt b/doc/payload-expression.txt
> index ceccfdaa..f1de0956 100644
> --- a/doc/payload-expression.txt
> +++ b/doc/payload-expression.txt
(...)
> @@ -833,6 +859,18 @@ filter input tcp option sack-perm exists counter
> filter input tcp option maxseg size lt 536
> --------------------
>
> +.matching MPTCP suboptions
> +--------------------
> +filter input tcp option mptcp subtype mp-join drop
> +--------------------
> +
> +[NOTE]
> +====================
> +Netfilter currently evaluates only the first MPTCP option found in the TCP
> +header. If a packet contains multiple MPTCP options, a rule attempting to match
> +the second option will never match.
Would it be interesting to give an example? e.g. a rule attempting to
match 'remove-addr', 'mp-prio' and 'mp-fail' (and 'mp-tcprst' in some
cases) are not going to catch anything when the traffic is emitted by
the current Linux kernel stack.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-09-30 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 14:14 [PATCH nft] doc: add MPTCP subtypes documentation to man page Fernando Fernandez Mancera
2026-09-30 18:38 ` Matthieu Baerts [this message]
2026-10-01 8:58 ` Fernando Fernandez Mancera
2026-10-06 17:06 ` Matthieu Baerts
2026-10-06 20:40 ` Fernando Fernandez Mancera
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=ef8c754d-616f-489f-b556-073efa491cd2@kernel.org \
--to=matttbe@kernel.org \
--cc=coreteam@netfilter.org \
--cc=fmancera@suse.de \
--cc=netfilter-devel@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 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.