From: Stephen Hemminger <shemminger@osdl.org>
To: Gergely Madarasz <gorgo@broadband.hu>
Cc: linux-net@vger.kernel.org, Neil Horman <nhorman@redhat.com>,
bridge@lists.osdl.org
Subject: Re: [Bridge] Re: tg3 bridge problems
Date: Mon, 10 Jan 2005 11:34:54 -0800 [thread overview]
Message-ID: <20050110113454.086ec0e2@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <20050110154506.GJ7529@thunderchild.debian.net>
On Mon, 10 Jan 2005 16:45:06 +0100
Gergely Madarasz <gorgo@broadband.hu> wrote:
> On Mon, Jan 10, 2005 at 10:05:56AM -0500, Neil Horman wrote:
> > Gergely Madarasz wrote:
> > >Hello,
> > >
> > >I've got a very strange problem. Lately I've been setting up my linux
> > >servers for network (layer2) redundancy with a bridge interface containing
> > >two ethernet interfaces connecting to two switches. So far I didn't have
> > >any problems with it, but now a very strange thing happens with a new
> > >server I'm installing. The server is an ibm x346 having two onboard
> > >BCM5721 cards, the switches are cisco 3550, and I've tested with kernel
> > >versions 2.6.10 and 2.4.28.
It could be the switch? Some switches require configuring the port as monitor
mode (othewise they do MAC filtering).
I have a machine with:
03:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02)
Subsystem: IBM: Unknown device 026f
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 28
Memory at c0200000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable
but haven't tried bridging with it.
prev parent reply other threads:[~2005-01-10 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 14:06 [Bridge] tg3 bridge problems Gergely Madarasz
2005-01-10 15:05 ` [Bridge] " Neil Horman
2005-01-10 15:45 ` Gergely Madarasz
2005-01-10 16:04 ` Neil Horman
2005-01-10 16:18 ` Gergely Madarasz
2005-01-10 17:40 ` Neil Horman
2005-01-10 19:11 ` Gergely Madarasz
2005-01-10 19:41 ` Neil Horman
2005-01-10 19:49 ` Gergely Madarasz
2005-01-10 19:53 ` Neil Horman
2005-01-10 20:09 ` Gergely Madarasz
2005-01-10 20:43 ` Neil Horman
2005-01-11 9:16 ` Gergely Madarasz
2005-01-11 4:06 ` Paul Schulz
2005-01-11 8:52 ` Gergely Madarasz
2005-01-11 12:36 ` Neil Horman
2005-01-11 12:58 ` Gergely Madarasz
2005-01-11 13:12 ` Neil Horman
2005-01-11 14:07 ` Gergely Madarasz
2005-01-11 20:19 ` dave
2005-01-12 9:21 ` Gergely Madarasz
2005-01-10 19:34 ` Stephen Hemminger [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=20050110113454.086ec0e2@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=gorgo@broadband.hu \
--cc=linux-net@vger.kernel.org \
--cc=nhorman@redhat.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