From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Redundant internet connections.
Date: Fri, 22 Jun 2007 18:57:51 +0000 [thread overview]
Message-ID: <467C1BAF.60403@riverviewtech.net> (raw)
In-Reply-To: <467A2354.1070805@riverviewtech.net>
On 06/21/07 17:35, Grant Taylor wrote:
> The problem with this method is that I have yet to get it to start
> re-using the primary route when it becomes available again.
After doing some more testing and investigation, I think I know why the
system appears to not be using the primary route. My test / lab setup
consists of a Linux router with two subnets bound to one interface (eth0
and eth0:1) and my (VMWare) test Linux system with two ethernet
interfaces bridged the the local LAN with one subnet on each interface.
I have two (as far as Linux is concerned) physical interfaces so that
I can have TX / RX counters for each interface to see which way the
traffic is going out. This worked fine to have the system fall from the
primary down to the secondary route when the primary route went away.
However I never saw the traffic from the test Linux system back to the
interface for the primary route. After doing some investigation I think
this is because the same MAC address is used for both the primary and
secondary routes, seeing as how both addresses are on the same physical
interface on my Linux router.
So, to test this, I took down the primary route, let the test Linux box
fall back to the backup route, which it did. Then I brought the primary
route back on line and waited. As expected the traffic did not start
using the primary route, presumably because of MAC addresses for routes
being cached with an association to a device. So, while the system was
pinging out to the world with the primary route brought back up, I
cleared entries from the local test Linux boxes ARP cache and all of the
sudden, traffic started going out the correct interface.
So, now I think that the method of having two equal cost (metric) routes
on the box will work. I'm now going to test where the two routes are
different MAC addresses to see if the traffic does indeed start using
the proper rout again (Seeing as how there should not be any confusion
with MAC addresses.)
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-22 18:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 7:05 [LARTC] Redundant internet connections Grant Taylor
2007-06-21 7:46 ` Salim S I
2007-06-21 14:46 ` Grant Taylor
2007-06-21 15:35 ` Peter Rabbitson
2007-06-21 15:52 ` Grant Taylor
2007-06-21 16:00 ` Peter Rabbitson
2007-06-21 16:23 ` Grant Taylor
2007-06-21 16:47 ` Peter Rabbitson
2007-06-21 17:02 ` Grant Taylor
2007-06-21 17:37 ` Peter Rabbitson
2007-06-21 18:27 ` Grant Taylor
2007-06-21 21:01 ` Alex Samad
2007-06-21 21:24 ` Grant Taylor
2007-06-21 22:18 ` Alex Samad
2007-06-21 22:23 ` Grant Taylor
2007-06-21 22:30 ` Alex Samad
2007-06-21 22:35 ` Grant Taylor
2007-06-21 22:39 ` Grant Taylor
2007-06-22 11:54 ` Gustavo Homem
2007-06-22 14:22 ` Grant Taylor
2007-06-22 14:57 ` Gustavo Homem
2007-06-22 15:59 ` Grant Taylor
2007-06-22 18:57 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 15:45 [LARTC] Redundant Internet connections Seth J. Blank
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=467C1BAF.60403@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.