All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoilo <zoilo@xs4all.nl>
To: "Craig H. Anderson" <craigha@attbi.com>, netfilter@lists.netfilter.org
Subject: Re: First iptables script - comments please
Date: Thu, 3 Oct 2002 20:58:42 +0200	[thread overview]
Message-ID: <02100320584201.02373@Lms> (raw)
In-Reply-To: <20021003172228.GC7407@gentoo.coot.net>

On Thursday 03 October 2002 19:22, Craig H. Anderson wrote:
> I've just tried iptables for the first time
> and would like comments on this simiple
> script.
>
> Gateway box with
>    cable modem on one NIC (eth2)
>    2 NIC's connected to local hubs.
>    local subnets are 10.0.0.0/24 and 10.0..1.0/24
>    only 10.0.0.0 is currently in use
>
> I am successful in getting to the internet
> with this script.
>
> # $Id: localFirewall,v 1.1 2002/10/03 16:31:21 craig Exp $
> iptables -t nat -A POSTROUTING -o eth2 -j MASQUERADE
> iptables -A FORWARD -s 10.0.0.0/24 -j ACCEPT
> iptables -A FORWARD -d 10.0.0.0/24 -j ACCEPT
> iptables -A FORWARD -j DROP

I would say that it's somewhat minimalistic, but OK.

Better to use "iptables -P FORWARD DROP" to establish default DROP-policy for 
the FORWARD chain, although you effectively achieve the same result by 
putting your DROP-rule at the end of the list.

A little further improvement may be obtained by adding "-i eth0" and "-o 
eth0" to your FORWARD rules.

And don't forget to handle INPUT and OUTPUT chains as well (default DROP 
policy).

-- 
Z.
------------------------------------------------------------
"If all you have is a hammer, everything looks like a nail."


      reply	other threads:[~2002-10-03 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 17:22 First iptables script - comments please Craig H. Anderson
2002-10-03 18:58 ` Zoilo [this message]

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=02100320584201.02373@Lms \
    --to=zoilo@xs4all.nl \
    --cc=craigha@attbi.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.