From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alexey Kashavkin <akashavkin@gmail.com>
Cc: netfilter@vger.kernel.org, ssuryaextr@gmail.com
Subject: Re: Clarification of the procedure for filtering IP option fields
Date: Thu, 30 Jan 2025 18:49:38 +0100 [thread overview]
Message-ID: <Z5u7sji0GX4Hfjci@calendula> (raw)
In-Reply-To: <123C96BD-BF4E-4EE5-8330-35B35E5A37CE@gmail.com>
Hi,
On Thu, Jan 30, 2025 at 04:52:29PM +0300, Alexey Kashavkin wrote:
> Hello,
>
> I am still figuring out the syntax for adding rules to filter IP
> options. Please, if anyone has an understanding of how this works
> give at least a short reply.
This 'type' field is redundant.
> I understand how the exthdr expression works in the kernel code. But
> so far there is still a question about specifying the type field,
> what is the purpose of this field here? There is also a question
> about other fields, let's take for example the IP option LSRR, it
> has an addr field. I assume, knowing this option from RFC791 it
> specifies IP addresses, but in the case of nft it is not so, this
> field has datatype intereger.
Yes, this should be at least 32-bits.
> With length and ptr fields it is clear, but with addr it is not.
> Please write how it works, what value is substituted in the addr
> field.
I remember to have mentioned the limitations of this with Stephen
(only a few ip options can be matched), Stephen told me this was good
enough for his use case at the time.
I regret I did not push back harder on this.
This extension really needs more work.
next prev parent reply other threads:[~2025-01-30 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 10:54 Clarification of the procedure for filtering IP option fields Alexey Kashavkin
2025-01-30 13:52 ` Alexey Kashavkin
2025-01-30 17:49 ` Pablo Neira Ayuso [this message]
2025-01-30 17:52 ` Pablo Neira Ayuso
2025-01-30 18:06 ` Pablo Neira Ayuso
2025-01-30 23:23 ` Alexey Kashavkin
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=Z5u7sji0GX4Hfjci@calendula \
--to=pablo@netfilter.org \
--cc=akashavkin@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=ssuryaextr@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.