From: Joel Newkirk <netfilter@newkirk.us>
To: Afshin Lamei <linux_st@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables management problem
Date: Wed, 4 Dec 2002 12:16:34 -0500 [thread overview]
Message-ID: <200212041216.34729.netfilter@newkirk.us> (raw)
In-Reply-To: <F139OSnJTycBI0c0deU0002173e@hotmail.com>
On Wednesday 04 December 2002 11:35 am, Afshin Lamei wrote:
> I have installed the Iptables 1.2.6a according to the netfilter's document,
> but It doesn't act as a service.
> Do I need to manually setup my firewall after each system boot up?
> --afshin
In the default setup, yes. One solution is to create a script (name it
firewall for convenience) in /etc/rc.d/init.d (well, at least with some
distros, such as RedHat) and links to it as /etc/rc.d/rc5.d/Sxxfirewall and
/etc/rc.d/rc3.d/Sxxfirewall (where xx is a number to start it at your chosen
point in the starting sequence, relative to the other Sxx script links for
each of those runlevels, again RedHat - your distro may differ). As long as
you have a valid script named (ie) /etc/rc.d/init.d/firewall then "service
firewall start" will start it. The links in rc5.d and rc3.d will cause it to
be automatically started in each of those runlevels. If you want, you can
write your script to support start, stop, and restart, the standard
parameters most such scripts support, but that isn't necessary to building
the firewall at system boot. If there are no parameters supported, then when
it is invoked during boot with the 'start' parameter the script will simply
ignore the parameter and execute anyway.
j
next prev parent reply other threads:[~2002-12-04 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 16:35 iptables management problem Afshin Lamei
2002-12-04 17:16 ` Joel Newkirk [this message]
2002-12-04 17:30 ` Rowan Reid
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=200212041216.34729.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=linux_st@hotmail.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