Ethernet Bridge development
 help / color / mirror / Atom feed
From: Mark Liggett <mliggett@btisystems.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: "bridge@lists.linux-foundation.org" <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] F13 bridge issues
Date: Thu, 14 Oct 2010 12:00:39 -0400	[thread overview]
Message-ID: <C8DCE7B7.69A7%mliggett@btisystems.com> (raw)
In-Reply-To: <20101013084639.5712c28c@nehalam>

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

Hi Stephen,

As you suspected, I believe the igb driver is at fault - I configured a bridge on the same machine using onboard tg3 cards.

The bridge worked fine and the fault did not occur until I SCP'd a file to the server on the igb card.  After which the bridge continued to work fine.

Thanks for your help.

Mark


On 13/10/2010 16:46, "Stephen Hemminger" <shemminger@linux-foundation.org> wrote:

On Wed, 13 Oct 2010 11:27:18 -0400
Mark Liggett <mliggett@btisystems.com> wrote:

> Hi everyone,
>
> I'm using Ethernet bridging on an up-to-date F13 system.  I've created a bridge adapter br0 and added eth2 and eth3 to it.  Everything works as expected for a short time before the 2 Ethernet cards used in the bridge start reporting millions of errors.  I confirmed this is the case on 2 separate systems (although both systems use Intel NICs).  To try to resolve this I've:
>
> - Compiled and installed the latest Intel igb driver 2.3.4
> - Installed the latest Fedora kernel 2.6.34.7-56
> - Uninstalled the standard bridge-utils 1.2-9, before compiling and installing version 1.4
>
> I've pastebin'd the system config here:  http://pastebin.ca/1960777
>
> You can see the errors listed on eth2 and eth3.  I've tried both setting the bridge up using /etc/sysconfig/network-scripts as well as manually (using brctl and ifconfig).
>
> My bridge/Ethernet interface configs are listed here: http://pastebin.ca/1960790
>
> Any suggestions would be greatly appreciated.
>
> Thanks,
>
> Mark

You might also be creating a packet loop?
Turn on spanning tree and find out.

--


[-- Attachment #2: Type: text/html, Size: 2385 bytes --]

      parent reply	other threads:[~2010-10-14 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 15:27 [Bridge] F13 bridge issues Mark Liggett
2010-10-13 15:45 ` Stephen Hemminger
2010-10-13 15:46 ` Stephen Hemminger
2010-10-13 16:14   ` Mark Liggett
2010-10-14 16:00   ` Mark Liggett [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=C8DCE7B7.69A7%mliggett@btisystems.com \
    --to=mliggett@btisystems.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=shemminger@linux-foundation.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