From: Ludwig Nussel <ludwig.nussel@suse.de>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [RFC] iptables namespaces
Date: Wed, 19 Sep 2007 17:05:47 +0200 [thread overview]
Message-ID: <20070919150547.GA2334@suse.de> (raw)
In-Reply-To: <20070908132810.GA19766@ekonomika.be>
Steven Van Acker wrote:
> [...]
> 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.
Correct me if I'm wrong but IIRC the tables are still committed
individually. Ie you cannot commit filter, nat and mangle in one
run.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
prev parent reply other threads:[~2007-09-19 15:05 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
2007-09-08 13:59 ` Jan Engelhardt
2007-09-19 15:05 ` Ludwig Nussel [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=20070919150547.GA2334@suse.de \
--to=ludwig.nussel@suse.de \
--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).