From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org, shivanib134@gmail.com
Subject: Re: [RFC nft PATCH] tests: shell: add a basic scapy test
Date: Wed, 30 Nov 2016 19:28:01 +0100 [thread overview]
Message-ID: <20161130182801.GB7892@salvia> (raw)
In-Reply-To: <20161130182704.GA7892@salvia>
On Wed, Nov 30, 2016 at 07:27:04PM +0100, Pablo Neira Ayuso wrote:
> On Wed, Nov 30, 2016 at 10:39:06AM +0100, Arturo Borrero Gonzalez wrote:
> > From: Arturo Borrero Gonzalez <arturo@debian.org>
> >
> > This test uses scapy to send a packet and test our packet/data path.
> > We grep the 'nft list ruleset' output for a counter increment.
> >
> > If we like this approach, then we could easily add more testcases
> > following the pattern in this patch.
>
> I think it's been several netfilter workshops already talking on this,
> but it never happens because nobody pushed this forward.
>
> If you can make this happen, it would great. Testing the datapath is
> something that we always wanted to have.
>
> Several ideas:
>
> * Check if you can use the dummy interface, so we make sure no other
> packets interfer with the tests.
>
> * You can probably augment this at some pointer to rely on the new
> nf_tables tracing infrastructure.
>
> Anyway, I agree that starting with something simple is good enough.
Only one more question left: Do you think you can slightly generalize
this so we decouple test files from the script? Similar to what we
have for nft-tests.py.
next prev parent reply other threads:[~2016-11-30 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 9:39 [RFC nft PATCH] tests: shell: add a basic scapy test Arturo Borrero Gonzalez
2016-11-30 18:27 ` Pablo Neira Ayuso
2016-11-30 18:28 ` Pablo Neira Ayuso [this message]
2016-12-01 8:10 ` Arturo Borrero Gonzalez
2016-12-01 10:45 ` Pablo Neira Ayuso
2016-12-01 11:04 ` Vadim Kochan
2016-12-01 15:05 ` Arturo Borrero Gonzalez
2016-12-01 16:52 ` 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=20161130182801.GB7892@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=shivanib134@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).