From: Steven Van Acker <deepstar+NRpGDEuW@singularity.be>
To: Jan Engelhardt <jengelh@computergmbh.de>, Martijn Lievaart <m@rtij.nl>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [RFC] iptables namespaces
Date: Sat, 8 Sep 2007 13:28:11 +0000 [thread overview]
Message-ID: <20070908132810.GA19766@ekonomika.be> (raw)
In-Reply-To: <Pine.LNX.4.64.0709080924090.25942@fbirervta.pbzchgretzou.qr>
On Sat, Sep 08, 2007 at 09:26:09AM +0200, Jan Engelhardt wrote:
> >iptables-restore takes a file as input, not a series of iptables
> >commands.
>
> Yes, it takes a file. And if you looked at it, yes, it takes iptables
> commands! (besides the table and counter markers)
>
> >This means I would have to edit the file manually, not
> >something I want to do with 7000 firewall rules.
>
> Where is the difference between...
>
> iptables -A INPUT -m foobar -j FOOBAR
>
> and adding
>
> -A INPUT -m foobar -j FOOBAR
>
> to the
>
> *filter
>
> section? (Otherwise, write a script, as suggested, or use a GUI ;-)
Hi,
it's remarkable that we have never tried it this way before.
I tested adding 10000 lines with iptables, then using iptables-save and
iptables-restore. The difference in speed is amazing. With iptables it
takes 5 minutes and 10 seconds, while iptables-restore takes 0.3
seconds.
Moreover, if there is an error in iptables-restore, none of the changes
are committed to kernelspace. So I no longer need to use fancy checking
while I'm loading my firewall rules.
Thank you both for the information :)
kind regards,
-- Steven
next prev parent reply other threads:[~2007-09-08 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 18:02 [RFC] iptables namespaces Steven Van Acker
2007-09-07 18:46 ` Maximilian Wilhelm
2007-09-07 19:06 ` Steven Van Acker
2007-09-07 21:09 ` Martijn Lievaart
2007-09-08 7:26 ` Jan Engelhardt
2007-09-08 13:28 ` Steven Van Acker [this message]
2007-09-08 13:59 ` Jan Engelhardt
2007-09-19 15:05 ` Ludwig Nussel
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=20070908132810.GA19766@ekonomika.be \
--to=deepstar+nrpgdeuw@singularity.be \
--cc=jengelh@computergmbh.de \
--cc=m@rtij.nl \
--cc=netfilter-devel@lists.netfilter.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 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).