From: Florian Westphal <fw@strlen.de>
To: Quentin Headen <qheaden@phaseshiftsoftware.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: Starting point in netfilter development
Date: Wed, 2 Jul 2014 22:43:23 +0200 [thread overview]
Message-ID: <20140702204323.GA22753@breakpoint.cc> (raw)
In-Reply-To: <CAFgy_YJ8wdPm6P2M_bPVXqbHzJ6oQxWT-3DmfQpikqPma=SDAA@mail.gmail.com>
Quentin Headen <qheaden@phaseshiftsoftware.com> wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > nftables is currently under active development; f.e. you could
> > add one of the missing iptables extensions such as hashlimit
> > or nfacct.
>
> Working on hashlimit for nftables sounds interesting.
Its not very beginner-friendly though.
nfacct *might* be a bit simpler.
Maybe someone else has a better idea.
> > nf.git and nf-next.git from kernel.org. git.netfilter.org
> > mostly hosts the userspace tools like iptables/nftables
> > and the associated libraries.
>
> So to work on hashlimit functionality for nftables, I'm guessing I
> would need to work with the code found on git.netfilter.org? Would it
> be mostly a userspace coding experience?
Yes, most of the functionality should be in userspace, but it
would need kernel support as well.
next prev parent reply other threads:[~2014-07-02 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:03 Starting point in netfilter development Quentin Headen
2014-06-30 15:22 ` Florian Westphal
2014-07-01 1:45 ` Quentin Headen
2014-07-02 20:43 ` Florian Westphal [this message]
2014-07-03 9:18 ` Pablo Neira Ayuso
2014-07-05 5:15 ` Quentin Headen
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=20140702204323.GA22753@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=qheaden@phaseshiftsoftware.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 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.