From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Multihomed Problem
Date: Tue, 11 Dec 2007 16:55:30 -0600 [thread overview]
Message-ID: <475F1562.7060207@riverviewtech.net> (raw)
In-Reply-To: <1197412206.19486.115.camel@grateful.d.umn.edu>
On 12/11/07 16:30, Matt Zagrabelny wrote:
> You wouldn't need to set up NAT if both IPs on the gnu/linux box are
> the gateways for the respective networks. Just enable forwarding:
Agreed. I answered the question as if the multihomed system was not the
router.
If the multihomed system is the router or if the router knows about all
subnets, direct routing (not NATing) would probably be the better approach.
> No NAT required, the linux box is aware of the subnets and will pass
> traffic happily between them.
So long as firewalling is not in the say, yes.
Grant. . . .
next prev parent reply other threads:[~2007-12-11 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 21:24 Multihomed Problem Jack Lauman
2007-12-11 22:04 ` Grant Taylor
2007-12-11 22:30 ` Matt Zagrabelny
2007-12-11 22:55 ` Grant Taylor [this message]
2007-12-12 19:09 ` Jack Lauman
2007-12-12 19:35 ` Matt Zagrabelny
2007-12-13 0:21 ` Grant Taylor
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=475F1562.7060207@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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