linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Problem with 2.4.24 e1000 and keepalived
Date: Wed, 7 Jan 2004 20:05:56 +0100	[thread overview]
Message-ID: <20040107200556.0d553c40.skraw@ithnet.com> (raw)

Hello all,

I am looking for confirmation for the following problem.
Setup is a simple pair of routers with 2 nics each, all e1000. If you start a
vrrp setup with keepalived and interface state is down during keepalived
startup, then the failover does not work. If the nics are UP during startup
everything works well. Now the kernel part of the story: the exact same setup
works with tulip cards.
Is there a difference regarding UP/DOWN state handling/events in e1000 and
tulip. e100 and eepro100 show the same problem btw.

Any hints are welcome

Regards,
Stephan

             reply	other threads:[~2004-01-07 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 19:05 Stephan von Krawczynski [this message]
2004-01-07 21:02 ` Problem with 2.4.24 e1000 and keepalived 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
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=20040107200556.0d553c40.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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).