From: Willy Tarreau <willy@w.ods.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Willy Tarreau <willy@w.ods.org>,
Stephan von Krawczynski <skraw@ithnet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Problem with 2.4.24 e1000 and keepalived
Date: Thu, 8 Jan 2004 09:46:05 +0100 [thread overview]
Message-ID: <20040108084605.GA9050@alpha.home.local> (raw)
In-Reply-To: <3FFD0FAE.8050705@candelatech.com>
On Thu, Jan 08, 2004 at 12:07:10AM -0800, Ben Greear wrote:
> No, I meant what I said: You have to tell many drivers to bring the
> interface
> up before they will attempt (or at least report) link negotiation.
> You do NOT have to give it an IP address or add any routes to it.
ah, OK. No, anyway, it is just a matter of wrongly detecting link state
after the link has been plugged while the interface was already UP, no
matter if an IP was set or not.
> But, I don't know about your particular program, I just suspect it
> is related to detecting link state. I think tg3 detects link when
> the interface is not UP, if you have some tg3 nics maybe you could
> try with them?
As far as I have tested, tg3 are fine WRT this.
Willy
next prev parent reply other threads:[~2004-01-08 8:46 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 [this message]
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
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=20040108084605.GA9050@alpha.home.local \
--to=willy@w.ods.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=skraw@ithnet.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;
as well as URLs for NNTP newsgroup(s).