From: Marcelo <terminus@iespana.es>
To: lartc@vger.kernel.org
Subject: [LARTC] dead onlink
Date: Wed, 29 Oct 2003 16:54:53 +0000 [thread overview]
Message-ID: <marc-lartc-106746139214825@msgid-missing> (raw)
Hello people:
I'm new in the forum. I've implemented the script for load balancing of
"Linux Advanced Routing & Traffic Control HowTo" and I've a question:
When I run the next command : "ip route" I get the folowing information:
--------------
192.168.0.32/27 dev eth0 proto kernel scope link src 192.168.0.33
192.168.0.96/27 dev eth2 proto kernel scope link src 192.168.0.97
192.168.0.64/27 dev eth1 proto kernel scope link src 192.168.0.65
192.168.0.128/27 dev eth3 proto kernel scope link src 192.168.0.129
127.0.0.0/8 dev lo scope link
default
nexthop via 192.168.0.126 dev eth2 weight 1 dead onlink
nexthop via 192.168.0.61 dev eth0 weight 1
-----------------------------
Is normal the part of "dead onlink" ?
Is it balancing the load between both internet providers?
Sorry for my English. I'm from Argentine.
Thanks in advance.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-10-29 16:54 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-106746139214825@msgid-missing \
--to=terminus@iespana.es \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox