All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Никита Винокуров" <vinokurov@mail.>
To: lartc@vger.kernel.org
Subject: [LARTC] further than dead gateway detection
Date: Mon, 03 Mar 2003 13:43:50 +0000	[thread overview]
Message-ID: <marc-lartc-104669924623485@msgid-missing> (raw)

Hi all!

I have  a set up of router with two ISP providers. Each on ADSL modem and with public IP address. I've the patch from Julian Anastasov applied (routed-2.4.20-9.diff).
External interfaces are: eth1 and eth2, internal is: eth0. The modems serve as gateways to my router, so, I simply set them as gateways on correspondent interfaces.

Multipath routing is  implemented as two nexthop's:

ip route add default table 222 proto static \
 nexthop via $GATEWAY1 dev eth1 weight 1 \
 nexthop via $GATEWAY2 dev eth2 weight 10

so when I plug-off the eth1 link to first modem, all the traffic moves to go through the eth2 and vice-versa. It works successfully.

The problem is that the most probably situation is not when one of my gateways is down (because it's really a modem and I have full access to it), but when the modem link to one of providers is down. So almost always I have the routes to be present in the system (I think because of the gateways are really up) and cached while one of my provider is down. The point is that the packets passed through the eth2 keep the same route even after my second provider fails (but gateway remains reachable) and they dont want to switch to the eth1. So any connection seems not working.

Please, help. How to detect that the link _behind_ a gateway is break? All the time gateways are reachable. _______________________

--
Nikita________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-03-03 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 13:43 Никита Винокуров [this message]
2003-03-03 15:55 ` [LARTC] further than dead gateway detection Esteban Ribicic

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=marc-lartc-104669924623485@msgid-missing \
    --to=vinokurov@mail. \
    --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.