All of lore.kernel.org
 help / color / mirror / Atom feed
From: christopher cuse <ccuse@tiscali.fr>
To: lartc@vger.kernel.org
Subject: [LARTC] concerning load sharing, failover, multiple means of egress
Date: Tue, 08 Apr 2003 15:49:25 +0000	[thread overview]
Message-ID: <marc-lartc-104981693814731@msgid-missing> (raw)

hi everyone,

i went thru the how-to and started into a configuration for a linux
router with 2 adsls connected. i created two routing tables, isp1 and
isp2 and the rules which assure that traffic to isp1 goes over isp1
link, etc. that all seems pretty clear.

where i am a bit unclear in testing was with the multiple path ip route
statement which leaves me with the following:

[root@drs0 ccuse]# ip route sh
192.168.1.0/24 dev eth1  scope link
192.168.0.0/24 dev eth0  scope link
127.0.0.0/8 dev lo  scope link
default
        nexthop via 192.168.0.10  dev eth0 weight 1 dead onlink
pervasive
        nexthop via 192.168.1.10  dev eth1 weight 1


from a few tests, everything seems to go out over the eth1 (192.168.1.1)
interface excepting packets destined for 192.168.0.0/24 (eth0)


could someone point me to more information on the meaning of "weight"
and its valid ranges.also, about the deterministic nature of interface
selection? in my example, there is no routing protocol, and the
assumption is that both interfaces could provide routes to the final
destination. given that, if an interface goes down, and the route is in
cache, what happens? is there a way to failover to the other interface?

many, many thanks!

christopher cuse


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

                 reply	other threads:[~2003-04-08 15:49 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-104981693814731@msgid-missing \
    --to=ccuse@tiscali.fr \
    --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.