Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Deepak Seshadri" <dseshadri@broadbandmaritime.com>
To: netfilter@lists.netfilter.org,
	Jason Williams <jwilliams@courtesymortgage.com>
Subject: Re: Saving IPTable rules..oops
Date: Wed, 29 Dec 2004 13:23:43 -0500	[thread overview]
Message-ID: <002501c4edd3$872fb6b0$0500a8c0@floydian> (raw)
In-Reply-To: 6.1.2.0.0.20041229095858.02518240@corpmail.courtesymortgage.com

> Morning.

Afternoon.

> Well, spent a better part of the night playing with IPTables. Tried out 
> some rules, tweaked this, broke that. Was a lot of fun.
>
> Anyway, as I am getting ready to make one of my servers go live, I 
> realized something that I completely overlooked. Very important thing I 
> might add.
>
> Basically, once you put all your rules into IPTables via the command line, 
> how do you save your rules? I saw a command, iptables-save, but that just 
> outputs the rules in a readable format.
>
> I started thinking and came up with the following:
>
> 1) Does iptables read the init script in /etc/init.d/ upon bootup of a 
> server/box and use those rules for the system?

YES.

> or
>
> 2) Does it read a plain text file some where an use those rules instead?

YES. /etc/sysconfig/iptables

> wasn't quite sure and since im going on 22 hours without sleep, im 
> positive I missed it some where.
>
> With that in mind, was hoping someone could fill in the details.
>
> IF it is the case the the system reads the iptables init script upon 
> bootup/restart, that means I need to work on my scripting. :)
>
> Anyways, hoping for a little clarity here.
>
> Cheers,
>
>
> Jason


You can do couple of things:
- After you enter your commands from a shell, you can do a *service iptables 
save*. All the commands that you had entered will be stored in the 
*iptables* file in /etc/sysconfig. By the way this is the file the system 
reads while boot up to load the firewall configuration.
- You can directly edit this file to add new commands (though it is not 
recommended, but I still do it 'coz it makes life easier) and then run 
*iptables-restore* to load the new configuration.

Hope this helps.

Deepak Seshadri 



  reply	other threads:[~2004-12-29 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 18:03 Saving IPTable rules..oops Jason Williams
2004-12-29 18:23 ` Deepak Seshadri [this message]
2004-12-30 20:39   ` Jason Williams
2004-12-30 20:52     ` Deepak Seshadri
2004-12-30 21:38       ` Jason Williams
2004-12-30 22:09         ` John A. Sullivan III
2004-12-29 18:32 ` John A. Sullivan III
2004-12-29 20:15   ` R. DuFresne
2004-12-29 20:29     ` Jason Opperisano
2004-12-30  6:33       ` R. DuFresne
2004-12-29 20:30     ` Les Mikesell
2004-12-29 22:29     ` John A. Sullivan III
2004-12-30  0:08       ` Alistair Tonner
2004-12-30  6:45       ` R. DuFresne
2004-12-29 18:35 ` John A. Sullivan III

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='002501c4edd3$872fb6b0$0500a8c0@floydian' \
    --to=dseshadri@broadbandmaritime.com \
    --cc=jwilliams@courtesymortgage.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox