Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: iptables-list <netfilter@lists.samba.org>
Subject: Re: forwarding (continued)
Date: Mon, 8 Jul 2002 16:28:00 +0100	[thread overview]
Message-ID: <200207081528.g68FS6807279@vulcan.rissington.net> (raw)
In-Reply-To: <000601c226ab$d5394ac0$8f01d6d1@nebuchadnezza>

On Monday 08 July 2002 5:23 pm, Tim wrote:

> > I don't quite understand why you have the line
> > 172.16.0.0      *               255.255.255.0   eth1
> > in the table ?
>
>  I have no idea how this got here to begin with, I certainly did no
> such configuration. (??)

Ah.   In that case you can blame the entire failure of this firewall to do 
what it's supposed to on the dreaded Firewall Reconfiguration Fairy, who 
comes along when you're not looking and messes with your routing table :-)

> Here is what Im going to do, Im going to remove all routes (except local)
> and re-establish a table that makes  more sense.

Sounds good to me.

> > By the way, can you ping from the firewall to either/both of the
> > machines ?

> Only if I have INPUT and OUTPUT rules in place.

Sounds like that would be a good thing to do (temporarily) just to make sure 
that A can talk to B, and B can reply to A, that B can talk to C, and C can 
reply to B, before taking the daring step of seeing whether A can talk to C 
through B and getting the reply back again as well :-)

 

Antony.


  reply	other threads:[~2002-07-08 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08  4:54 forwarding (continued) Tim
2002-07-08  2:05 ` Antony Stone
2002-07-08  6:40   ` Tim
2002-07-08  7:54     ` Antony Stone
2002-07-08 16:23       ` Tim
2002-07-08 15:28         ` Antony Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-08  2:24 George Vieira
2002-07-08  2:20 George Vieira

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=200207081528.g68FS6807279@vulcan.rissington.net \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.samba.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