From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stephen Suryaputra <ssuryaextr@gmail.com>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: add support for matching IPv4 options
Date: Sat, 1 Jun 2019 02:22:30 +0200 [thread overview]
Message-ID: <20190601002230.bo6dhdf3lhlkknqq@salvia> (raw)
In-Reply-To: <20190531193558.GB4276@ubuntu>
On Fri, May 31, 2019 at 03:35:58PM -0400, Stephen Suryaputra wrote:
> On Fri, May 31, 2019 at 07:11:01PM +0200, Pablo Neira Ayuso wrote:
> > > +/* find the offset to specified option or the header beyond the options
> > > + * if target < 0.
> > > + *
> > > + * Note that *offset is used as input/output parameter, and if it is not zero,
> > > + * then it must be a valid offset to an inner IPv4 header. This can be used
> > > + * to explore inner IPv4 header, eg. ICMP error messages.
> >
> > In other extension headers (IPv6 and TCP options) this offset is used
> > to match for a field inside the extension / option.
> >
> > So this semantics you describe here are slightly different, right?
>
> It is the same as the IPv6 one. The offset returned is the offset to the
> specific option (target) or the byte beyond the options if the target
> isn't specified (< 0).
Thanks for explaining. So you are using ipv6_find_hdr() as reference,
but not sure this offset parameter is useful for this patchset since
this is always set to zero, do you have plans to use this in a follow
up patchset?
[...]
> > > + if (tb[NFTA_EXTHDR_DREG])
> > > + return &nft_exthdr_ipv4_ops;
> > > + }
> > > + break;
> >
> > Then, from the _eval() path:
> >
> > You have to replace iph->version == 4 check abive, you could use
> > skb->protocol instead, and check for htons(ETH_P_IP) packets.
>
> A bit lost. Did you mean this?
>
> static int ipv4_find_option(struct net *net, struct sk_buff *skb,
> » » » unsigned int *offset, int target,
> » » » unsigned short *fragoff, int *flags)
> {
> ...
> » iph = skb_header_pointer(skb, *offset, sizeof(_iph), &_iph);
> » if (!iph || skb->protocol != htons(ETH_P_IP))
> » » return -EBADMSG;
I mean, you make this check upfront from the _eval() path, ie.
static void nft_exthdr_ipv4_eval(const struct nft_expr *expr,
...
{
...
if (skb->protocol != htons(ETH_P_IP))
goto err;
Thanks.
next prev parent reply other threads:[~2019-06-01 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 9:38 [PATCH nf-next] netfilter: add support for matching IPv4 options Stephen Suryaputra
2019-05-31 17:11 ` Pablo Neira Ayuso
2019-05-31 19:35 ` Stephen Suryaputra
2019-06-01 0:22 ` Pablo Neira Ayuso [this message]
2019-06-01 8:27 ` Florian Westphal
2019-06-01 8:40 ` Pablo Neira Ayuso
2019-06-01 8:53 ` Florian Westphal
2019-06-01 15:04 ` Stephen Suryaputra
2019-06-03 12:30 ` Pablo Neira Ayuso
2019-06-02 2:27 ` Stephen Suryaputra
2019-06-10 15:50 ` 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=20190601002230.bo6dhdf3lhlkknqq@salvia \
--to=pablo@netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox