From: Manish Kathuria <manish@tuxspace.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems in Dead Gateway Detection / Failover - Multiple
Date: Thu, 26 Jan 2006 13:41:18 +0000 [thread overview]
Message-ID: <43D8CEAE.3010006@tuxspace.com> (raw)
Hello,
I have configured a load balancing router using Julian's patches and as
described in "nano.txt" for two ISP links as shown below.
ISP 1 ISP 2
. .
| |
| |
| |
| WAN WAN |
+-\-+ +-\-+
| | | |
|R1 | GW1 GW2 |R2 |
| |------. --------| |
| | | | | |
+---+ | | +---+
EXT1 | | EXT2
+\----\-+
| |
| LINUX |
| ROUTER|
| |
| |
| |
+---/---+
| INT IF
|
|
|
/----------------\
| LAN |
| |
\----------------/
LAN NETWORK = 192.168.100.0/24
INT IF = 192.168.100.1
ISP1 NETWORK = 10.20.30.128/29
R1 - ROUTER1
GW1 = 10.20.30.129
EXT1 = 10.20.30.130
ISP2 NETWORK = 172.16.32.128/29
R2 - ROUTER2
GW2 = 172.16.32.129
EXT2 = 172.16.32.130
Both the ISPs have provided /29 subnets of Public IPs. The above
mentioned addresses are just for example.
The gateways for both the ISPs are routers placed at the same location
which are further connected through Radio Link and Leased Line.
Things work fine as long as both the ISP links are alive. While testing
the dead gateway detection and failover functionality we observed that
if we make the first hop gateway (i.e Router R1 or R2) of one of the
ISPs dead by either disconnecting the ethernet cable between Linux
Router and R1/R2 or by switching off the gateway (R1/R2) itself, dead
gateway detection takes place and failover to the other ISP takes place.
However, if there is a problem in the ISP connectivity at any of the
subsequent hops, there is no dead gateway detection and failover also
does not take place. I have tested this on various linux kernels from
2.4 as well as 2.6 series.
Somehow I have never faced a similar problem before and things have been
working perfectly. In real life situation here, the first hop gateway is
rarely going to be down so dead gateway detection and failover is going
to be required whenever there is some connectivity problem at any of the
later hops. So that's where dead gateway detection needs to work.
What could be the reason ? How can this be resolved ? I would appreciate
any pointers or suggestions.
Thanks,
Manish Kathuria
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-01-26 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 13:41 Manish Kathuria [this message]
2006-01-29 19:50 ` [LARTC] Problems in Dead Gateway Detection / Failover - gypsy
2006-01-30 3:50 ` Manish Kathuria
2006-04-15 13:58 ` [LARTC] Problems in Dead Gateway Detection / Failover - Multiple Eduardo Fernández
2006-04-17 7:14 ` Re:[LARTC] Problems in Dead Gateway Detection / Failover - Shashikant Mundlik
2006-04-17 14:01 ` [LARTC] Problems in Dead Gateway Detection / Failover Alessandro Ren
2006-04-17 15:16 ` Alessandro Ren
2006-04-17 15:22 ` Shashikant Mundlik
2006-04-17 15:52 ` Shashikant Mundlik
2006-04-17 16:30 ` [LARTC] Problems in Dead Gateway Detection / LinuXKiD
2006-04-17 17:11 ` [LARTC] Problems in Dead Gateway Detection / Failover Alessandro Ren
2006-04-21 1:49 ` [LARTC] Problems in Dead Gateway Detection / Failover - Multiple Manish Kathuria
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=43D8CEAE.3010006@tuxspace.com \
--to=manish@tuxspace.com \
--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.