Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Visham Ramsurrun <vishamr2000@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Starting a fw
Date: Fri, 8 Jul 2005 09:34:20 +0400	[thread overview]
Message-ID: <9927912d0507072234673f1aa0@mail.gmail.com> (raw)

Hi to all,

I was once told that in order to start a firewall automatically when a
machine boots, we must make sure that the init process calls the
script by making a symbolic link to that file in the /etc/rc.d/rcX.d
directories.

I have found that there is a file called S08iptables (kernel 2.4.20-8)
containing startup commands for iptables service. Do i delete it and
then put the symbolic link to my script there or just leave it?

Let's say I have a firewall script called fw.sh with the following rules in it:

#!/bin/bash
IPT=/sbin/iptables

$IPT -F
$IPT -X
$IPT -P INPUT DROP
$IPT -P OUTPUT DROP
$IPT -P FORWARD DROP

$IPT -A FORWARD -i eth0 -o eth0 -s 192.168.10.0/24 -d 192.168.10.0/24
-m state --state NEW,ESTABLISHED,RELATED -p icmp --icmp-type echo
request -j ACCEPT

$IPT -A FORWARD -i eth0 -o eth0 -s 192.168.10.0/24 -d 192.168.10.0/24
-m state --state NEW,ESTABLISHED,RELATED -p icmp --icmp-type echo
reply -j ACCEPT

What steps (where to create symbolic links, at which runlevel, etc)
should I take in order to have this script be started automatically
when PC boots up. How can I make sure that it is this firewall script
that is running and all packets are being checked against these rules?

Thx in advance..

Warm regards,
Visham


             reply	other threads:[~2005-07-08  5:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  5:34 Visham Ramsurrun [this message]
2005-07-08  5:47 ` Starting a fw Robert Vangel
2005-07-08  6:00   ` Venkata Narayana
2005-07-08 13:12 ` /dev/rob0
     [not found] ` <9927912d05071022336896dbb@mail.gmail.com>
2005-07-11  7:35   ` Robert Vangel

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=9927912d0507072234673f1aa0@mail.gmail.com \
    --to=vishamr2000@gmail.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