netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Laura Garcia Liebana <nevola@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] extensions: libip6t_frag: Add translation to nft
Date: Mon, 6 Jun 2016 13:35:30 +0200	[thread overview]
Message-ID: <20160606113530.GA6995@salvia> (raw)
In-Reply-To: <20160602165756.GA21013@sonyv>

On Thu, Jun 02, 2016 at 06:57:58PM +0200, Laura Garcia Liebana wrote:
> Add translation for frag to nftables. Not supported yet in nft: fraglen,
> fragfirst and fraglast.

You can provide translations for fragfirst and fraglast.

'--fragfirst' is actually frag-off 0.
and '--fraglast' is more-fragments 1.

Note that because there is no 1:1 mapping, it doesn't mean you can
translate things.

And regarding --fraglen, if you look at
iptables/extensions/libip6t_frag.c, you'll see:

        case O_FRAGLEN:
                /*
                 * As of Linux 3.0, the kernel does not check for
                 * fraglen at all.
                 */
                if (cb->invert)
                        fraginfo->invflags |= IP6T_FRAG_INV_LEN;
                fraginfo->flags |= IP6T_FRAG_LEN;
                break;

Then, browsing:

http://lxr.free-electrons.com/source/net/ipv6/netfilter/ip6t_frag.c

shows no references to IP6T_FRAG_LEN in the kernel, so this confirms
this option was already deprecated time ago and the comment in the
iptables source code is correct.

Please, respin and send a v2 including this useful information on the
commit message so we keep this in the record.

      reply	other threads:[~2016-06-06 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 16:57 [PATCH] extensions: libip6t_frag: Add translation to nft Laura Garcia Liebana
2016-06-06 11:35 ` Pablo Neira Ayuso [this message]

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=20160606113530.GA6995@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=nevola@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;
as well as URLs for NNTP newsgroup(s).