From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: Victor Julien <victor@nk.nl>,
netfilter@lists.netfilter.org,
netfilter-devel@lists.netfilter.org
Subject: Re: Creating rules without the /sbin/iptables command?
Date: Wed, 17 Mar 2004 18:04:42 -0500 [thread overview]
Message-ID: <1079564682.2112.1.camel@localhost> (raw)
In-Reply-To: <1079551538.1424.23.camel@anduril.intranet.cartel-securite.net>
On Wed, 2004-03-17 at 14:25, Cedric Blancher wrote:
> Le mer 17/03/2004 à 19:46, Victor Julien a écrit :
> > My program (written in c) creates rules by opening a pipe to
> > /sbin/iptables. However this is quite slow with large rulessets and on
> > slow hardware. Is there another way, like an iptables librarycall or
> > something?
>
> You could use iptables libs that stand in /usr/lib/iptables, just like
> iptables does.
>
> You should however ask netfilter developpers mailing list.
>
> Cc : netfilter-devel@lists.netfilter.org
The above solution is probably better than mine but I write out my new
rules to a file in iptables-save format and then use iptables-restore -n
<filename>. This is dramatically faster than calling iptables - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
prev parent reply other threads:[~2004-03-17 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 18:46 Creating rules without the /sbin/iptables command? Victor Julien
2004-03-17 19:25 ` Cedric Blancher
2004-03-17 20:59 ` Victor Julien
2004-03-18 8:56 ` Cedric Blancher
2004-03-17 21:34 ` Henrik Nordstrom
2004-03-17 23:04 ` John A. Sullivan III [this message]
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=1079564682.2112.1.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=blancher@cartel-securite.fr \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=victor@nk.nl \
/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