From: Neil Horman <nhorman@redhat.com>
To: Gergely Madarasz <gorgo@broadband.hu>
Cc: linux-net@vger.kernel.org, bridge@lists.osdl.org
Subject: [Bridge] Re: tg3 bridge problems
Date: Mon, 10 Jan 2005 14:41:34 -0500 [thread overview]
Message-ID: <41E2DA6E.8090703@redhat.com> (raw)
In-Reply-To: <20050110191133.GM7529@thunderchild.debian.net>
Gergely Madarasz wrote:
> On Mon, Jan 10, 2005 at 12:40:57PM -0500, Neil Horman wrote:
>
>>Gergely Madarasz wrote:
>>
>>>On Mon, Jan 10, 2005 at 11:04:55AM -0500, Neil Horman wrote:
>>>
>>>
>>>>Strange. My concern was that the tg3 interface has its hardware reset
>>>>whenever its set to be up, and part of that is a resetting of its
>>>>receive mode. If for some reason IFF_PROMISC was cleared after you set
>>>>it using brctl, the interface might be taken out of promisc mode. Do
>>>>you have any iptables rules running that might drop bpdus?
>>>
>>>
>>>No iptables rules az all. Btw iptables wouldn't prevent tcpdump from
>>>seeing the packets, would it?
>>>Could it be that the driver perhaps has a problem setting promisc mode
>>>when resetting the hardware?
>>>
>>
>>Not really sure about this. One experiment is worth a thousand guesses
>>I suppose....... I'll try and let you know. :)
>
>
> I did some other checks, like adding an explicit ifconfig eth0 promisc,
> then looking at tcpdump output - I didn't see any stray packets like I
> usually do, just ethernet broadcasts and unicasts to my mac, this also
> points to a problem that the ethernet interface is actually not in
> promisc, while the driver thinks it is.
>
> And it is probably not a driver-only issue. I've got older machines with
> tg3 running fine with bridge (with an older tg3 driver), and eth1 on the
> same machine also runs fine. On another machine I tested today, an IBM
> x326, the same thing happens - eth0 broken, eth1 fine. Would access to one
> of these machines help? :)
>
> Greg
I've got a tg3 card here. I'll try re-create it as soon as I have time.
Just out of curiosity, are you running tcpdump against the physical
interface or the bridged interface? I do recall some issues involving
using PF_PACKET on virtual interfaces, that might cause you to not see
some packets that the physical interface really does receive.
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
next prev parent reply other threads:[~2005-01-10 19:41 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 [this message]
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
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=41E2DA6E.8090703@redhat.com \
--to=nhorman@redhat.com \
--cc=bridge@lists.osdl.org \
--cc=gorgo@broadband.hu \
--cc=linux-net@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