From: Florian Westphal <fw@strlen.de>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: does nft 'tcp option ... exists' work?
Date: Mon, 4 Dec 2023 14:01:15 +0100 [thread overview]
Message-ID: <20231204130115.GA29636@breakpoint.cc> (raw)
In-Reply-To: <CAHo-OoyOh_6AOjCUrF8qZR-vuf=uhy_8WwzyFURwP_7=3jsWeA@mail.gmail.com>
Maciej Żenczykowski <zenczykowski@gmail.com> wrote:
> wrt. the fix, perhaps this should be fixed both in the kernel and in userspace?
> it seems wrong to have unpredictable endian-ness dependent kernel logic,
> but a userspace fix/workaround would be easier to deploy...
Right.
> Is there some way I could feed raw nf bytecode in via nft syntax (if
> no... should support for this be added?) ?
You could try this:
tcp option @34,8,8 == 34
(where 34 is the kind/option you are looking for).
next prev parent reply other threads:[~2023-12-04 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 12:24 does nft 'tcp option ... exists' work? Maciej Żenczykowski
2023-12-03 12:50 ` Maciej Żenczykowski
2023-12-03 13:13 ` Florian Westphal
2023-12-04 9:43 ` Florian Westphal
2023-12-04 10:48 ` Pablo Neira Ayuso
2023-12-04 12:38 ` Maciej Żenczykowski
2023-12-04 13:01 ` Florian Westphal [this message]
2023-12-04 13:20 ` Maciej Żenczykowski
2023-12-04 13:33 ` Florian Westphal
2023-12-04 23:01 ` Maciej Żenczykowski
2023-12-05 1:00 ` [PATCH nft] parser: tcpopt: fix tcp option parsing with NUM + length field Florian Westphal
2023-12-05 11:44 ` Pablo Neira Ayuso
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=20231204130115.GA29636@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zenczykowski@gmail.com \
/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.