From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bridging two subnets selectively using routing
Date: Sat, 03 Nov 2007 00:39:24 +0000 [thread overview]
Message-ID: <472BC33C.6010107@riverviewtech.net> (raw)
In-Reply-To: <20071101005039.GA4906@triplehelix.org>
On 10/31/07 19:50, Joshua Kwan wrote:
> What am I doing wrong? Is this a job for iptables? I feel like I can
> do this with just routing table magic.
As Corey said, make sure that IP Forwarding is enabled on A1.
You are setting your self up for a very weird scenario. Probably what
would be the easiest for long term would be to put a third network
between your two routers, AR and BR. This way you end up with the
following type of scenario:
+----+ +----+
| AI | | BI |
+-+--+ +--+-+
| |
+-+--+ +--+-+
---( Net A )---+ AR +---( Net C )---+ BR +---( Net B )---
| +----+ +----+ |
| |
| +----+ |
+-------+ A1 +----------------------------+
+----+
With this type of set up, you can configure both AR and BR that each can
reach the others network via the other router on network C. I.e. AR can
reach Net B via BR's IP on Net C. Likewise BR can reach Net A via AR's
IP on Net C. This way, each and every computer on both networks A and B
can reach any host they want to via their default gateway AR or BR
respectively. This may be a little more work to set up initially, but
it is very simple routing that will be very easy to maintain for a long
time. In this scenario Net C can very simply be a cross over cable
between routers AR and BR.
Another option is to enable routing on A1 and tell A2, A3, and A4 that
they can reach B1 via A1 and likewise tell B1 that it can reach a2, A3,
and A4 via A1. Thus you have a bi-directional routing set up between
just the four additional hosts. The main disadvantage of this set up is
that each and every host that wants to communicate across networks will
have to have its own routing entries set up to pick the correct
direction to route traffic to. So if you only have two or three hosts
on each network and you can not do the additional network (C) between
the two routers, this will work.
There are some other things that you can do to allow the hosts to
communicate across the networks like bridging and / or proxy ARP.
However seeing as how you have different subnets on Net A and Net B, you
will very likely be doing routing or multi-homing on all hosts to
support bridging and / or proxy ARP.
I think your best bet is to do the additional network (C) between the
two routers AR and BR.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-11-03 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 0:50 [LARTC] Bridging two subnets selectively using routing Joshua Kwan
2007-11-02 20:24 ` Corey Hickey
2007-11-03 0:39 ` Grant Taylor [this message]
2007-11-03 0:51 ` Grant Taylor
2007-11-03 4:35 ` Corey Hickey
2007-11-04 20:14 ` 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=472BC33C.6010107@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@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 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.