Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Internal ip exiting network on firewall external nic despight rule
Date: Fri, 20 Sep 2002 22:54:16 +0100	[thread overview]
Message-ID: <20020920215417.UBMV295.mta06-svc.ntlworld.com@there> (raw)
In-Reply-To: <000501c260ec$0cb7ddc0$0801a8c0@s3ac>

On Friday 20 September 2002 10:24 pm, Rowan Reid wrote:

> http://www.e-infomax.com/ipmasq/howto/examples/rc.firewall-2.4-stronger
>
> My firewall ruleset is a slight modification of the above link.

From what you have said so far, I don't think your ruleset is the problem 
(except possibly for a certain misunderstanding about the difference between 
INPUT and FORWARD chains...?).

I just had a look at that ruleset, and I'm very surprised at the use of 
$UNIVERSE all over the place - as I mentioned in a previous mail in this 
thread, it is quite redundant no matter where it appears (in other words, 
leaving it out of any rule creates precisely the same meaning, and is 
generally easier to understand), and in several of the examples where it 
appears it is actually rather pointless, eg:

iptables -A INPUT -s $somewhere -d $universe -j DROP

There is absolutely no purpose in having $universe (= 0.0.0.0/0) in such a 
rule.


I think the problem is your physical network setup - you should not have a 
direct link between the internal and external interfaces of your firewall.

Antony.

-- 

Most people are aware that the Universe is big.

 - Paul Davies, Professor of Theoretical Physics


  reply	other threads:[~2002-09-20 21:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 18:37 Internal ip exiting network on firewall external nic despight rule Rowan Reid
2002-09-20 19:05 ` Antony Stone
2002-09-20 20:59   ` Rowan Reid
2002-09-20 21:36     ` Antony Stone
2002-09-20 21:58       ` Rowan Reid
2002-09-20 22:43         ` Antony Stone
2002-09-20 23:10           ` Rowan Reid
2002-09-20 23:32             ` Antony Stone
2002-09-20 19:13 ` Tom Eastep
2002-09-20 19:11   ` Rowan Reid
2002-09-20 19:34     ` Antony Stone
2002-09-20 19:40       ` Tom Eastep
2002-09-20 21:24       ` Rowan Reid
2002-09-20 21:54         ` Antony Stone [this message]
2002-09-20 22:26           ` Rowan Reid
2002-09-20 23:01             ` Antony Stone
2002-09-20 23:13               ` Rowan Reid
2002-09-20 23:37                 ` Antony Stone
2002-09-21  1:00                 ` Tom Eastep
2002-09-21 13:01             ` Anders Fugmann
2002-09-20 19:36     ` Tom Eastep
2002-09-20 19:53     ` Alistair Tonner
     [not found] <000d01c260e8$df710380$0801a8c0@s3ac>
2002-09-20 21:44 ` Antony Stone

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=20020920215417.UBMV295.mta06-svc.ntlworld.com@there \
    --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