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 RESEND nf-next] netfilter: add support for matching IPv4 options
Date: Wed, 19 Jun 2019 19:18:32 +0200 [thread overview]
Message-ID: <20190619171832.om7losybbkysuk4r@salvia> (raw)
In-Reply-To: <20190611120912.3825-1-ssuryaextr@gmail.com>
On Tue, Jun 11, 2019 at 08:09:12AM -0400, Stephen Suryaputra wrote:
[...]
> diff --git a/net/netfilter/nft_exthdr.c b/net/netfilter/nft_exthdr.c
> index a940c9fd9045..4155a32fade7 100644
> --- a/net/netfilter/nft_exthdr.c
> +++ b/net/netfilter/nft_exthdr.c
[...]
> +static int ipv4_find_option(struct net *net, struct sk_buff *skb,
> + unsigned int *offset, int target,
> + unsigned short *fragoff, int *flags)
> +{
[...]
> + switch (target) {
> + case IPOPT_SSRR:
> + case IPOPT_LSRR:
[...]
> + case IPOPT_RR:
[...]
> + case IPOPT_RA:
[...]
> + default:
> + /* Either not supported or not a specific search, treated as
> + * found
> + */
> + found = true;
> + if (target >= 0) {
> + target = -EOPNOTSUPP;
> + break;
> + }
Rules with this options will load fine:
ip option eol type 1
ip option noop type 1
ip option sec type 1
ip option timestamp type 1
ip option rr type 1
ip option sid type 1
However, they will not ever match I think.
found is set to true, but target is set to EOPNOTSUPP, then...
[...]
> +static void nft_exthdr_ipv4_eval(const struct nft_expr *expr,
> + struct nft_regs *regs,
> + const struct nft_pktinfo *pkt)
> +{
> + struct nft_exthdr *priv = nft_expr_priv(expr);
> + u32 *dest = ®s->data[priv->dreg];
> + struct sk_buff *skb = pkt->skb;
> + unsigned int offset;
> + int err;
> +
> + if (skb->protocol != htons(ETH_P_IP))
> + goto err;
> +
> + err = ipv4_find_option(nft_net(pkt), skb, &offset, priv->type, NULL, NULL);
... ipv4_find_option() returns -EOPNOTSUPP which says header does
not exist.
> + if (priv->flags & NFT_EXTHDR_F_PRESENT) {
> + *dest = (err >= 0);
> + return;
> + } else if (err < 0) {
> + goto err;
> + }
next prev parent reply other threads:[~2019-06-19 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 12:09 [PATCH RESEND nf-next] netfilter: add support for matching IPv4 options Stephen Suryaputra
2019-06-18 15:31 ` Pablo Neira Ayuso
2019-06-18 14:13 ` Stephen Suryaputra
2019-06-19 16:50 ` Pablo Neira Ayuso
2019-06-19 17:18 ` Pablo Neira Ayuso [this message]
2019-06-19 17:58 ` Stephen Suryaputra
2019-06-19 18:00 ` 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=20190619171832.om7losybbkysuk4r@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