netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] tests/shell: add chain validations tests
Date: Tue, 22 Mar 2016 20:20:19 +0100	[thread overview]
Message-ID: <20160322192019.GA7551@salvia> (raw)
In-Reply-To: <145865193086.6118.9200431804176858644.stgit@nfdev2.cica.es>

On Tue, Mar 22, 2016 at 02:06:09PM +0100, Arturo Borrero Gonzalez wrote:
> Some basic test regarding chains: jumps and validations.
>
> Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
> ---
> NOTE: the testcases/chains/0009masquerade_jump_1 file fails, seems like a bug
> in the kernel validation. Needs more investigation.

I can see this there:

> +$NFT add chain t output {type nat hook output priority 0 \; }

We only support masquerade from postrouting.

static struct xt_target masquerade_tg_reg __read_mostly = {                      
        .name           = "MASQUERADE",                                          
        .family         = NFPROTO_IPV4,                                          
        .target         = masquerade_tg,                                         
        .targetsize     = sizeof(struct nf_nat_ipv4_multi_range_compat),         
        .table          = "nat",                                                 
        .hooks          = 1 << NF_INET_POST_ROUTING,   

BTW, it would be good to add more tests to exercise the chain loop
detection code.

Please, fix and resubmit, thanks.

  reply	other threads:[~2016-03-22 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 13:06 [nft PATCH] tests/shell: add chain validations tests Arturo Borrero Gonzalez
2016-03-22 19:20 ` Pablo Neira Ayuso [this message]
2016-03-23  7:44   ` Arturo Borrero Gonzalez
2016-03-29 11:16     ` Pablo Neira Ayuso
2016-03-23  0:09 ` Mart Frauenlob
2016-03-23  8:02   ` Arturo Borrero Gonzalez

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=20160322192019.GA7551@salvia \
    --to=pablo@netfilter.org \
    --cc=arturo.borrero.glez@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    /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).