From: Philip Craig <philipc@snapgear.com>
To: Darren.Reed@Sun.COM
Cc: netfilter-devel@lists.netfilter.org,
Phil Dibowitz <phil@ipom.com>,
Henrik Nordstrom <henrik@henriknordstrom.net>
Subject: Re: Developing a user space library for filtering
Date: Wed, 23 May 2007 10:29:27 +1000 [thread overview]
Message-ID: <46538AE7.8040405@snapgear.com> (raw)
In-Reply-To: <465382DB.3080106@Sun.COM>
Darren.Reed@Sun.COM wrote:
> Henrik Nordstrom wrote:
>> Having an API which says things like "Add a rule to accept this kind of
>> traffic" is only possible cross the different firewall implementations
>> if there also is a defined firewall ruleset structure requirement
>> defining suitable places in the ruleset where this API can make it's
>> modifications.
>>
>>
>
> Which means that coming up with a design that works won't
> necessarily be a slam-dunk.
It means the API must an interface to a firewall policy, not to a kernel
mechanism. For example, the API should enable you to tell shorewall
that you want to accept something, rather than directly generating
an iptables rule. (Although a simple implementation for the case where
you have no firewall policy may directly generate an iptables rule.)
next prev parent reply other threads:[~2007-05-23 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 22:27 Developing a user space library for filtering Darren.Reed
2007-05-21 22:47 ` Carl-Daniel Hailfinger
2007-05-21 22:52 ` Darren.Reed
2007-05-22 6:27 ` Jan Engelhardt
2007-05-22 6:46 ` Patrick Schaaf
2007-05-22 20:50 ` Darren.Reed
2007-05-22 21:14 ` Phil Dibowitz
2007-05-22 22:58 ` Henrik Nordstrom
2007-05-22 23:55 ` Darren.Reed
2007-05-23 0:29 ` Philip Craig [this message]
2007-05-23 8:19 ` Henrik Nordstrom
2007-05-22 7:11 ` Allen Francom
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=46538AE7.8040405@snapgear.com \
--to=philipc@snapgear.com \
--cc=Darren.Reed@Sun.COM \
--cc=henrik@henriknordstrom.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=phil@ipom.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.