From: "Deepak Seshadri" <dseshadri@broadbandmaritime.com>
To: Jason Williams <jwilliams@courtesymortgage.com>,
netfilter@lists.netfilter.org
Subject: Re: Saving IPTable rules..oops
Date: Thu, 30 Dec 2004 15:52:37 -0500 [thread overview]
Message-ID: <002d01c4eeb1$7f6a1fe0$0500a8c0@floydian> (raw)
In-Reply-To: 6.1.2.0.0.20041230123544.02691b78@corpmail.courtesymortgage.com
From: "Jason Williams" <jwilliams@courtesymortgage.com>
To: <netfilter@lists.netfilter.org>
Sent: Thursday, December 30, 2004 3:39 PM
Subject: Re: Saving IPTable rules..oops
> At 10:23 AM 12/29/2004, you wrote:
>>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.
>
> Appreciate the help and feedback on this. Makes sense now.
> One queston regarding the /etc/sysconfig/iptables file. In this file, can
> I put my variables in there? Such as: INET_IP=212.122.131.34,
> INET_IFACE="eth0" and so forth?
> Or does that need to go somewhere else?
I don't think you can put your variables in /etc/sysconfig/iptables file. It
follows a particular pattern which is not that difficult to learn.
If you want to use variables and stuff, you gotta write your own script file
and run it at bootup. I use do this way when my firewall rules were less
than 50 lines.
Now my firewall rules are more than 500 lines so I edit the
/etc/sysconfig/iptables file directly. It is just an efficient way to load
the rules through this file.
>>Hope this helps.
>>
>>Deepak Seshadri
>
> Thanks!
>
> Jason
>
>
next prev parent reply other threads:[~2004-12-30 20:52 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
2004-12-30 20:39 ` Jason Williams
2004-12-30 20:52 ` Deepak Seshadri [this message]
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='002d01c4eeb1$7f6a1fe0$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 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.