From: Willy Tarreau <willy@w.ods.org>
To: Jonathan Lundell <linux@lundell-bros.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Problem with 2.4.24 e1000 and keepalived
Date: Fri, 9 Jan 2004 01:45:25 +0100 [thread overview]
Message-ID: <20040109004525.GB545@alpha.home.local> (raw)
In-Reply-To: <p0602042fbc2347a37845@[192.168.0.3]>
On Thu, Jan 08, 2004 at 09:49:20AM -0800, Jonathan Lundell wrote:
> One place where you might want to know: an HA system where a
> redundant interface is available to be configured in place of an
> active interface. We'd like to know the state of the link on the
> backup interface, which is logically down, as an indication that it's
> hooked up and ready to go.
It's exactly under these conditions that I discovered the problem. None
of the interface was usable by the bonding driver, although one of them
was properly connected !
> It's unfortunate that the two conditions are conflated by most net drivers.
IMHO, saying "most net drivers" is unfair : tg3, tulip, 3c59x, starfire,
realtek, sis900, dl2k, pcnet32, and IIRC sunhme are OK. eepro100 is nearly
OK but has this annoying bug, and only older 10 Mbps drivers don't report
their status, often because the chip itself doesn't know.
Willy
next prev parent reply other threads:[~2004-01-09 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 19:05 Stephan von Krawczynski
2004-01-07 21:02 ` Willy Tarreau
2004-01-08 2:45 ` Ben Greear
2004-01-08 5:20 ` Willy Tarreau
2004-01-08 8:07 ` Ben Greear
2004-01-08 8:46 ` Willy Tarreau
2004-01-08 8:14 ` Stephan von Krawczynski
2004-01-08 8:47 ` Willy Tarreau
2004-01-08 17:49 ` Jonathan Lundell
2004-01-09 0:45 ` Willy Tarreau [this message]
2004-01-09 1:00 ` Jonathan Lundell
2004-01-09 12:18 ` Stephan von Krawczynski
2004-01-09 18:43 ` Jonathan Lundell
2004-01-09 23:56 ` Stephan von Krawczynski
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=20040109004525.GB545@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux@lundell-bros.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®