All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Dead gateway detection
Date: Fri, 09 Aug 2002 12:48:19 +0000	[thread overview]
Message-ID: <marc-lartc-102889743909267@msgid-missing> (raw)


	Hello,

On Fri, 9 Aug 2002, Laurens van Alphen wrote:

> Q1: In the Nano-HOWTO on your site, it says to include these statements:
> "ip route append prohibit default table <tablename> metric 1 proto
> static"
> Why? What does it do? If I use these I can't connect to the Internet,
> without them I can.

	The reason can be that you have other rule/route settings.

	The purpose is: traffic using source addresses from failed
links should not try to use another alive link (some ISPs do not
allow spoofing from our side). Such prohibit rules avoid using
less-specific routes from other tables if the previous route is
deleted (metric 0).

> Q2: I have the following multipath route to the Internet:
> "default  proto static
>         nexthop via GW1 dev eth1 weight 1
>         nexthop via GW2 dev eth2 weight 1"
> If I unplug eth2 the second route is never marked as 'dead', why?
> Only if I 'ifconfig eth2 down' the second route is marked dead. I
> thought the patches would detect this?

	Linux detects failed gateways and does not use them but
the nexthops remain alive. Dead are only the routes administratively
marked as such. This is the current way.

> Thanks,
>
> --
> Laurens van Alphen
> Keen on dots

Regards

--
Julian Anastasov <ja@ssi.bg>

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

                 reply	other threads:[~2002-08-09 12:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-102889743909267@msgid-missing \
    --to=ja@ssi.bg \
    --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.