From: bert hubert <ahu@ds9a.nl>
To: Julian Anastasov <ja@ssi.bg>
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG/WANT TO FIX] Equal Cost Multipath Broken in 2.4.x
Date: Thu, 20 Dec 2001 12:29:27 +0100 [thread overview]
Message-ID: <20011220122927.A12949@outpost.ds9a.nl> (raw)
In-Reply-To: <20011220112728.A11112@outpost.ds9a.nl> <Pine.LNX.4.33.0112201316210.4670-100000@l>
In-Reply-To: <Pine.LNX.4.33.0112201316210.4670-100000@l>; from ja@ssi.bg on Thu, Dec 20, 2001 at 01:21:30PM +0200
On Thu, Dec 20, 2001 at 01:21:30PM +0200, Julian Anastasov wrote:
> > 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
>
> Yes, I remember people to report for this problem for long
> time but I was not able to reproduce it. May be it could be fixed
> with the following change (only compiled):
Your patch does not appear to relate to iproute-20010824. I think I've found
the problem, however. I think there has been an API change between 2.2 and
2.4. 'ip' compiled under 2.2 will not properly configure ECMP on 2.4!
If I recompile tc under 2.4, the problem disappears.
Maybe ip should warn against this? Should be easy to do.
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 prev parent reply other threads:[~2001-12-20 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 10:27 bert hubert
2001-12-20 11:21 ` Julian Anastasov
2001-12-20 11:29 ` bert hubert [this message]
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=20011220122927.A12949@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=ja@ssi.bg \
--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®