netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Quentin Headen <qheaden@phaseshiftsoftware.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Starting point in netfilter development
Date: Mon, 30 Jun 2014 17:22:45 +0200	[thread overview]
Message-ID: <20140630152245.GC9515@breakpoint.cc> (raw)
In-Reply-To: <CAFgy_YLvGwc3y3R3vv0hdTPsQ+yX7eUW8YUppef9xJQsdH9frw@mail.gmail.com>

Quentin Headen <qheaden@phaseshiftsoftware.com> wrote:
> * Is there an active IRC channel for netfilter developers?

Not that I am aware of.  There is #netfilter on freenode,
sometimes developers are also on this channel though its mostly
dealing with end-user questions.

> * When pulling repository changes, do I use git.netfilter.org, or the
> main Linux kernel git repo?

nf.git and nf-next.git from kernel.org. git.netfilter.org
mostly hosts the userspace tools like iptables/nftables
and the associated libraries.

> * Where is a good place for me to get started with netfilter contributions?

It depends on wheter you want to focus on kernel or userspace,
and on what area you'd like to work on.

nftables is currently under active development; f.e. you could
add one of the missing iptables extensions such as hashlimit
or nfacct.

At least for hashlimit I suspect that an nftables equivalent should
not 'copy' hashlimit to nftables but instead take advantage
of nftables' architecture by e.g. using register(s) as input
(as compared to the packet).

Would avoid avoid adding all the hashlimit-mode/src-mask options
from the iptables match in the nft version, and it would be more
flexible because the data extraction/compaction would be in userspace.

Alternatively, you could look at the open bug reports/feature wishlist
items:
http://bugzilla.netfilter.org/buglist.cgi?product=nftables&component=nft&resolution=---

> * Is there any bug tracking done outside of the mailing list?

There is bugzilla.netfilter.org that some people use.

  reply	other threads:[~2014-06-30 15:22 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 [this message]
2014-07-01  1:45   ` Quentin Headen
2014-07-02 20:43     ` Florian Westphal
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=20140630152245.GC9515@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 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).