* iptables management problem
@ 2002-12-04 16:35 Afshin Lamei
2002-12-04 17:16 ` Joel Newkirk
2002-12-04 17:30 ` Rowan Reid
0 siblings, 2 replies; 3+ messages in thread
From: Afshin Lamei @ 2002-12-04 16:35 UTC (permalink / raw)
To: netfilter
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
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: iptables management problem
2002-12-04 16:35 iptables management problem Afshin Lamei
@ 2002-12-04 17:16 ` Joel Newkirk
2002-12-04 17:30 ` Rowan Reid
1 sibling, 0 replies; 3+ messages in thread
From: Joel Newkirk @ 2002-12-04 17:16 UTC (permalink / raw)
To: Afshin Lamei; +Cc: netfilter
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: iptables management problem
2002-12-04 16:35 iptables management problem Afshin Lamei
2002-12-04 17:16 ` Joel Newkirk
@ 2002-12-04 17:30 ` Rowan Reid
1 sibling, 0 replies; 3+ messages in thread
From: Rowan Reid @ 2002-12-04 17:30 UTC (permalink / raw)
To: 'Afshin Lamei', netfilter
>
> 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
>
IPTABLES actually is a ruleset for the kernel regarding network traffic.
In order to to enable the firewall at each boot you need to create a
boot script that loads the rules on each boot.
Read the following link
http://www.e-infomax.com/ipmasq/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-12-04 17:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-04 16:35 iptables management problem Afshin Lamei
2002-12-04 17:16 ` Joel Newkirk
2002-12-04 17:30 ` Rowan Reid
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox