From: joshk@triplehelix.org (Joshua Kwan)
To: lartc@vger.kernel.org
Subject: [LARTC] Bridging two subnets selectively using routing
Date: Thu, 01 Nov 2007 00:50:39 +0000 [thread overview]
Message-ID: <20071101005039.GA4906@triplehelix.org> (raw)
Hi LARTC,
I have two networks that I manage, A and B. They both have their own
primary gateways for hosts on the network, let's call them AR and BR.
There is another box, A1, which lives on network A but also has a wire
connecting it to a switch on network B. My goal is to let hosts on B
access three particular hosts on A's subnet (192.168.4.0/24) and let
hosts on A access one particular host on B's subnet (10.3.0.0/24).
Suppose the IP addresses of the machines I wish to address on either
network are A2, A3, A4 and B1.
A1 has IP 10.3.0.13 on network B and 192.168.4.10 on network A. Is it
possible to just tell the gateways for each network:
on BR: ip route add {A2, A3, A4} via 10.3.0.13
on AR: ip route add B1 via 192.168.4.10
But when I do that, ping does something like:
PING A2 56(84) bytes of data.
From BR: Redirect Host (new nexthop: 10.3.0.13)
and doesn't actually report success on the ping.
What am I doing wrong? Is this a job for iptables? I feel like I can do
this with just routing table magic.
Thanks,
--
Joshua Kwan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-11-01 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 0:50 Joshua Kwan [this message]
2007-11-02 20:24 ` [LARTC] Bridging two subnets selectively using routing Corey Hickey
2007-11-03 0:39 ` Grant Taylor
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=20071101005039.GA4906@triplehelix.org \
--to=joshk@triplehelix.org \
--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.