netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maximilian Wilhelm <max@rfc2324.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [RFC] iptables namespaces
Date: Fri, 7 Sep 2007 20:46:42 +0200	[thread overview]
Message-ID: <20070907184642.GA4728@outback.rfc2324.org> (raw)
In-Reply-To: <20070907180204.GA460@ekonomika.be>

Am Friday, den  7 September hub Steven Van Acker folgendes in die Tasten:

Hi!

> I've been thinking about some kind of namespaces in iptables where one can 
> switch from one set of rules to another set of rules by flicking a switch.

> In our current setup, we have about 7000 firewall rules. Every time the 
> rules get updated, all of them are removed and uploaded again by a script.
> Loading all these rules takes a while (let's say a minute, I'm not sure).

> The result is that for 1 minute, some traffic can get through the firewall rules
> while other can not. We have had problems with spam getting through to 
> mailservers behind the firewall, because not all firewall rules were loaded.

That problem can be solved.
man iptables-restore

> Using namespaces would make it possible to load all rules in another namespace
> and when all rules are loaded, a switch can be toggled to switch over to the new
> ruleset atomically.

That would be most probably nothing different to a iptables-restore.
If you want to emulate that, load your 7000 iptables rules on a
temp-machine, use iptables-save, copy the file to your firewalls and run
iptables-restore

Ciao
max
-- 
	Follow the white penguin.

  reply	other threads:[~2007-09-07 18:46 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 [this message]
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

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=20070907184642.GA4728@outback.rfc2324.org \
    --to=max@rfc2324.org \
    --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).