From: Ben Greear <greearb@candelatech.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: 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, 08 Jan 2004 00:07:10 -0800 [thread overview]
Message-ID: <3FFD0FAE.8050705@candelatech.com> (raw)
In-Reply-To: <20040108052000.GA8829@alpha.home.local>
Willy Tarreau wrote:
> Hi Ben,
>
> On Wed, Jan 07, 2004 at 06:45:04PM -0800, Ben Greear wrote:
>
>
>>You have to bring the interface 'UP' before it will detect link,
>>with something like: ifconfig eth2 up
>
>
> Don't you mean "after" instead of "before" here ? Because the case where
> it doesn't work is when everything is set up while the cable is unplugged,
> but conversely, if the system goes up with the cable plugged, setting the
> interface UP detects the link as UP and works. I believe that the problem
> is related to setting the interface UP with nothing plugged into it.
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.
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?
Ben
>
> Cheers,
> Willy
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2004-01-08 8:07 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 [this message]
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
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=3FFD0FAE.8050705@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=skraw@ithnet.com \
--cc=willy@w.ods.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).