All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: How to test the kernel netfilter logic?
Date: Tue, 26 May 2020 01:12:13 +0200	[thread overview]
Message-ID: <20200526011213.37df67a1@redhat.com> (raw)
In-Reply-To: <8499b3da-fef3-2e42-289a-c824837d8ca3@virtuozzo.com>

On Mon, 25 May 2020 17:00:24 +0300
Konstantin Khorenko <khorenko@virtuozzo.com> wrote:

> On 05/25/2020 03:50 PM, Stefano Brivio wrote:
> > Hi Konstantin,
> >
> > On Mon, 25 May 2020 11:37:57 +0300
> > Konstantin Khorenko <khorenko@virtuozzo.com> wrote:
> >  
> >> but did not find netfilter tests in kernel git repo as well.  
> >
> > Have a look at tools/testing/selftests/netfilter/, some of the tests
> > there actually send traffic and check the outcome.  
> 
> Hi Stefano,
> 
> thank you very much for the answer!
> 
> Yes, you are right, i know about that place, i just thought it's just
> for "smoke" testing:

Well, I'd say it's a bit more than that, some tests there cover
specific functionalities rather extensively. Still:

> "iptables" and "nftables" repos have many more testcases (for add/del
> rules), so i thought there is some additional place with similar very
> detailed tests for kernel part.

...I'm not aware of any (except for ipset cases that actually test both
sides with packets, see http://git.netfilter.org/ipset/tree/tests).

Sure, I think it would be great to have something with actual traffic
at the same level of detail as nft tests, though.

-- 
Stefano


  reply	other threads:[~2020-05-25 23:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  8:37 How to test the kernel netfilter logic? Konstantin Khorenko
2020-05-25 12:50 ` Stefano Brivio
2020-05-25 14:00   ` Konstantin Khorenko
2020-05-25 23:12     ` Stefano Brivio [this message]
2020-05-26  9:03       ` Konstantin Khorenko

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=20200526011213.37df67a1@redhat.com \
    --to=sbrivio@redhat.com \
    --cc=khorenko@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.