From: Anders Fugmann <afu@fugmann.dhs.org>
To: Jared Brick <jbrick@videotron.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: Chain traversal with multiple internal IP subnets.
Date: Mon, 23 Sep 2002 08:23:07 +0200 [thread overview]
Message-ID: <3D8EB34B.7080401@fugmann.dhs.org> (raw)
In-Reply-To: 1032724445.1352.22.camel@neo.matrix.ca.
Jared Brick wrote:
> Hello everybody,
>
> However the other gateway is a Linux box with two IP addresses (it only
> acts as a gateway for two of the subnets) using Iptables.
I'm not sure of your setup. Do you have one network interface per ip, or
two ip's for the same interface?
> The gateway
> itself has static routes so that it can route between the different
> subnets, including the subnet for which it has no IP address. My
> question in which chain will a packet traverse when it is traveling
> between two different internal subnets. I think it is the FORWARD chain
> but my colleague feels it would be the OUTPUT chain. I ask because I am
> having trouble routing between the internal networks.
If you hare only using one network interface, then you will have
troubles routing between the two subnets. Please see the recent thread
in which this was discussed:
"Internal ip exiting network on firewall external nic despight rule"
(http://lists.netfilter.org/pipermail/netfilter/2002-September/038510.html)
> If anyone has any experience with a similar set up, any help would be
> much appreciated.
It seems to me that you do not need netfilter at all, as netfilter does
not route packets. I recommend that you setup your linux router and make
it work without netfilter. Then, if you want to restrict communication
between the subnets, use netfilter.
Hope it helps.
Anders Fugmann
next prev parent reply other threads:[~2002-09-23 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1032724445.1352.22.camel@neo.matrix.ca.>
2002-09-23 1:22 ` Chain traversal with multiple internal IP subnets Antony Stone
2002-09-23 6:23 ` Anders Fugmann [this message]
2002-09-22 19:54 Jared Brick
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=3D8EB34B.7080401@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=jbrick@videotron.ca \
--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.