All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: Netfilter User Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: Preferred way of preserving firewall rules on system reboots?
Date: Thu, 13 May 2004 11:11:29 -0500	[thread overview]
Message-ID: <40A39E31.40905@pbl.ca> (raw)
In-Reply-To: <1084460291.1771.183.camel@anduril.intranet.cartel-securite.net>

Cedric Blancher wrote:
> Le jeu 13/05/2004 à 16:48, Aleksandar Milivojevic a écrit :
> 
>>What is your preferred way of preserving firewall configuration on 
>>firewall reboots?  I know this is probably distribution specific.
> 
> 
> Every time I need to save the ruleset :
> 
> 	iptables-save > /etc/firewall
> 
> Then, in a startup script (/etc/init.d/networking on my Debian), I add :
> 
> 	iptables-restore < /etc/firewall

This is something what Red Hat's init.d script is doing (if called with 
"save").  However, using this approach, there's no space left for any 
comments.  It is questionable I would still remember why I have some 
"special" set of rules one year from now, if there was no comments in 
the file.  And it makes very hard for somebody else to change anything I 
created (something obvious to me might not be obvious to somebody else, 
hack it might not be obvious to me couple of months down the road).  I 
find having comments in configuration files very important.

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


      parent reply	other threads:[~2004-05-13 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 14:48 Preferred way of preserving firewall rules on system reboots? Aleksandar Milivojevic
2004-05-13 14:58 ` Cedric Blancher
2004-05-13 15:44   ` Alistair Tonner
2004-05-13 16:11   ` Aleksandar Milivojevic [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=40A39E31.40905@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --cc=blancher@cartel-securite.fr \
    --cc=netfilter@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 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.