All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andy Loukes" <andy@loukes.com>
To: <netfilter-devel@vger.kernel.org>
Subject: Netfilter development project
Date: Wed, 13 Aug 2008 18:20:15 +0100	[thread overview]
Message-ID: <000501c8fd68$da840390$8f8c0ab0$@com> (raw)

My company needs to develop two netfilter applications.

First a simple daemon which listens on a tcp socket for messages which
inform it to add or remove specific iptables rules. It needs to be
secure, very high performance and deal with multiple concurrent 
requests. We currently use iptables rules, but when I get time I'm going
to try out using IPSet as it seems more appropriate.

Second an accounting daemon, it needs to connect to another server using
a to-be-defined protocol to update the packet and byte counts, in and
out per source ip address.

I have proposed to my company that I send this out to the netfilter-dev 
list because we don't have the resource available at the moment and our 
dev team aren't particularly familiar with netfilter.

We are obviously prepared to pay!

The company is based in London although geography doesn't need to be 
particularly relevant.

Please contact me with a brief CV, any examples of code and why you 
think you should do it!

Clearly if these applications could be made useful to the wider 
community then it would be better for everyone.

I hope this is an appropriate list for this request, I did check the rules!

Regards

Andy









             reply	other threads:[~2008-08-13 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 17:20 Andy Loukes [this message]
2008-08-13 18:13 ` Netfilter development project Pablo Neira Ayuso
     [not found]   ` <002101c90c64$f40dae50$dc290af0$@com>
2008-09-02  8:46     ` high number of rule changes per second (was Re: Netfilter development project) Pablo Neira Ayuso
2008-09-04  7:40       ` Jesper Dangaard Brouer

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='000501c8fd68$da840390$8f8c0ab0$@com' \
    --to=andy@loukes.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.