All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Ben Greear <greearb@candelatech.com>
Cc: willy@w.ods.org, 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:14:41 +0100	[thread overview]
Message-ID: <20040108091441.3ff81b53.skraw@ithnet.com> (raw)
In-Reply-To: <3FFCC430.4060804@candelatech.com>

On Wed, 07 Jan 2004 18:45:04 -0800
Ben Greear <greearb@candelatech.com> wrote:

> Willy Tarreau wrote:
> > Hi Stephan,
> > [...]
> > What I noticed is that if you load the driver while the cable is unplugged,
> > and then plug it, the MII status says the link is still down.
> > Unfortunately, the only e100 I have access to are in prod at a customer's
> > and I really cannot make tests there.
> 
> You have to bring the interface 'UP' before it will detect link,
> with something like:  ifconfig eth2 up
> 
> Could that be the problem?
> 
> Ben

Hi Ben,

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)

in comparison to:

- let all interfaces plugged in
- reboot box
- log in
- start keepalived
- watch it work as expected

Regards,
Stephan



  parent reply	other threads:[~2004-01-08  8:15 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 [this message]
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=20040108091441.3ff81b53.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.