Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Help: Iptables rules
Date: Thu, 15 Jan 2004 01:24:58 +0000	[thread overview]
Message-ID: <200401150124.58475.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <OF22A0643A.09EB3DB8-ON88256E1C.00058296-88256E1C.0005DD77@statsus.com>

On Thursday 15 January 2004 1:04 am, Minh Cao wrote:

> Hi,
>
> I am new to iptables.
> Please help me to create a rules, which allows everything in and out both
> interfaces.

I wonder why you want this - because it is an open router - there is no point 
in using netfilter (which is used to block things) if you want to allow 
everything....

> What I have but not worked:
> iptables -A FORWARD -i $EXTIF -o $INTIF -j ACCEPT
> iptables -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
>
> iptables -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

What you have shown above looks as though it will do what you want (it is, of 
course just a router, very insecure, and does not qualify as a firewall, but 
it meets your specification).

Some questions:

1. Do you have packet forwarding turned on in the kernel (cat 
/proc/sys/net/ipv4/ip_forward)?

2. What are the default policies on your netfilter chains (iptables -L)?

3. You say the above has not worked - how have you tested it?

4. Do packets get across the router in either direction (internal to external? 
external to internal)?

5. Have you read Oskar Andreasson's netfilter tutorial at 
http://iptables-tutorial.frozentux.net, referenced on the netfilter home page 
http://www.netfilter.org/documentation/index.html#documentation-tutorials?

6. Did the machine work as a simple router before you tried adding netfilter 
rules?

Regards,

Antony.

-- 
Software development can be quick, high quality, or low cost.

The customer gets to pick any two out of three.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-01-15  1:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  1:04 Help: Iptables rules Minh Cao
2004-01-15  1:24 ` Antony Stone [this message]
     [not found] <OFE1656F2A.7FFED69B-ON88256E1C.000829BB-88256E1C.00088CCC@statsus.com>
2004-01-15  1:39 ` Antony Stone
2004-01-15  1:41 ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-01-15 19:57 Minh Cao
2004-01-15 20:11 ` Aldo S. Lagana
2004-01-15 21:53 ` Antony Stone
2004-01-15 23:13 Minh Cao
2004-01-15 23:27 ` Antony Stone
2004-01-16  2:04 ` Alexis

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=200401150124.58475.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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