From: Jonathan Lundell <linux@lundell-bros.com>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Problem with 2.4.24 e1000 and keepalived
Date: Thu, 8 Jan 2004 09:49:20 -0800 [thread overview]
Message-ID: <p0602042fbc2347a37845@[192.168.0.3]> (raw)
In-Reply-To: <20040108084758.GB9050@alpha.home.local>
At 9:47am +0100 1/8/04, Willy Tarreau wrote:
>On Thu, Jan 08, 2004 at 09:14:41AM +0100, Stephan von Krawczynski wrote:
>> the situation is like this (exactly this works flawlessly with tulip):
>>
>> - unplug all interfaces from the switches
>> - reboot box
>> - plug in _one_ interface
>> - log into the box (yes, network works flawlessly)
>> - start keepalived
>> - now plug in rest of the interfaces
>> - watch keepalived do _nothing_ (seems no UP event shows up)
>
>I agree with this description, and would add :
> - mii-diag ethX or ethtool ethX report link down
Which is, IMO, a bug, albeit a kind of specification bug, given the
way the drivers tend to be written. An Ethernet link can be up or
down independent of the logical up/down state of the interface, and
with most drivers the link state is hidden as long as the interface
is logically down.
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 unfortunate that the two conditions are conflated by most net drivers.
--
/Jonathan Lundell.
next prev parent reply other threads:[~2004-01-08 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 19:05 Problem with 2.4.24 e1000 and keepalived 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 [this message]
2004-01-09 0:45 ` Willy Tarreau
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='p0602042fbc2347a37845@[192.168.0.3]' \
--to=linux@lundell-bros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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;
as well as URLs for NNTP newsgroup(s).