From: bert hubert <ahu@ds9a.nl>
To: kuznet@ms2.inr.ac.ru
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [BUG/WANT TO FIX] Equal Cost Multipath Broken in 2.4.x
Date: Thu, 20 Dec 2001 11:27:28 +0100 [thread overview]
Message-ID: <20011220112728.A11112@outpost.ds9a.nl> (raw)
# ip ro add dev eth0 default nexthop via 10.0.0.1 dev eth0 nexthop via
10.0.0.202 dev eth0
# ip ro ls
10.0.0.0/8 dev eth0 proto kernel scope link src 10.0.0.11
default
nexthop via 10.0.0.1 dev eth0 weight 1 dead
nexthop via 10.0.0.202 dev eth0 weight 1
10.0.0.1 however is far from dead, if we add yet another nexthop:
# ip ro add dev eth0 default nexthop via 10.10.10.10 dev eth0 nexthop via
10.0.0.1 dev eth0 nexthop via 10.0.0.202 dev eth0
# ip ro ls
10.0.0.0/8 dev eth0 proto kernel scope link src 10.0.0.11
default
nexthop via 10.10.10.10 dev eth0 weight 1 dead
nexthop via 10.0.0.1 dev eth0 weight 1
nexthop via 10.0.0.202 dev eth0 weight 1
This first nexthop is *always* declared dead. Linux 2.4.x, iproute 20010824.
If anybody can point me in the direction of this problem, it must be known
as it has been there for a *long* time, it would be appreciated. I'll try to
fix it.
Thanks!
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
next reply other threads:[~2001-12-20 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 10:27 bert hubert [this message]
2001-12-20 11:21 ` Julian Anastasov
2001-12-20 11:29 ` bert hubert
2001-12-20 12:13 ` Julian Anastasov
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=20011220112728.A11112@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®