From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 10 Jan 2005 11:34:54 -0800 From: Stephen Hemminger Subject: Re: [Bridge] Re: tg3 bridge problems Message-ID: <20050110113454.086ec0e2@dxpl.pdx.osdl.net> In-Reply-To: <20050110154506.GJ7529@thunderchild.debian.net> References: <20050110140638.GH7529@thunderchild.debian.net> <41E299D4.2010605@redhat.com> <20050110154506.GJ7529@thunderchild.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gergely Madarasz Cc: linux-net@vger.kernel.org, Neil Horman , bridge@lists.osdl.org On Mon, 10 Jan 2005 16:45:06 +0100 Gergely Madarasz 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.