public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@ecsc.co.uk>
To: lao nightwolf <laonightwolf@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: use of bonding in kernel 2.4.19
Date: 10 Oct 2002 12:02:10 +0100	[thread overview]
Message-ID: <1034247730.1490.77.camel@lemsip> (raw)
In-Reply-To: <F27YI9IJsaJbqJGNzsc000001ea@hotmail.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On Thu, 2002-10-10 at 08:44, lao nightwolf wrote:
> Hello,
> 
> I've read in some posts to this list that there's a bug in kernel 2.4.19 
> stable regarding the use of bonding.
> 
> I've setup bonding myself yesterday with the patch from 
> sourceforge.net/projects/bonding and everything works as it should be
> 
> bond0 is bringing up both my nic's eth0 and eth1.
> 
> Is this because I use an external patch? Or can someone give me more 
> explanation about using bonding in kernel 2.4.19. Or should I wait till 
> 2.4.20 is released (does someone know when this will be? +/-)

The bonding problem in 2.4.19 is with the default boding code in there.
If you update to the latest bonding patch, then that should fix it.

FYI: This patch does the job for me:
http://www.scaramanga.co.uk/kernel/ECSC-2.4.19/02_bonding-fixes.diff.gz

its from 2.4.20-preX where it was fixed.

-- 
// Gianni Tedesco (gianni at ecsc dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-10-10 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10  7:44 use of bonding in kernel 2.4.19 lao nightwolf
2002-10-10 11:02 ` Gianni Tedesco [this message]

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=1034247730.1490.77.camel@lemsip \
    --to=gianni@ecsc.co.uk \
    --cc=laonightwolf@hotmail.com \
    --cc=linux-kernel@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