From: Nguyen Dinh Nam <64vn@cardvn.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] please guide me ...with regard to multipath dynamic routing
Date: Tue, 08 Feb 2005 12:55:51 +0000 [thread overview]
Message-ID: <4208B6D7.1040503@cardvn.net> (raw)
In-Reply-To: <003201c50d24$5e650670$8d00150a@dreammac>
So you have to write a daemon to ping the remote gateway, and if ping
fails, the daemon will remove that nexthop from the multipath route. The
dead gateway detection patch can't help you in this case.
That's why I created this project, download and run it, and everything
solved, it's lack of documentation, so you're welcome to write it in the
Wiki.
http://selab.edu.ms/twiki/bin/view/Networking/RoutesKeeperProject
Pankaj Agarwal wrote:
> Hi,
>
> There's some very silly mistake i've done in my configuration. I did
> by reading material on web. I'm enclosing my configuration script
> below. The problem is its not routing the trafic from other interface
> in case the first interface is down....which should be the wright
> case. Kindly please guide me what i can do to make it
> work..dynamically.. Also there is a very common situation which many
> of you might have face...the interface which is gateway for my device
> is my local router interface...and there's almost no chance of that's
> being down ever...How can one configure ip route to consider the ISP
> ends IP as the gateway when deciding on link status...
>
> Thanks,
>
> Pankaj Agarwal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-02-08 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 14:52 [LARTC] please guide me ...with regard to multipath dynamic routing in case of link failure Pankaj Agarwal
2005-02-08 12:55 ` Nguyen Dinh Nam [this message]
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=4208B6D7.1040503@cardvn.net \
--to=64vn@cardvn.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.