All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mitchell <jmitchell@ll.mit.edu>
To: Ben Greear <greearb@candelatech.com>
Cc: "bridge@lists.linux-foundation.org" <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] Bridge suddenly only passes traffic if in promiscuous mode
Date: Tue, 8 Feb 2011 14:50:47 -0500	[thread overview]
Message-ID: <4D519E97.40706@ll.mit.edu> (raw)
In-Reply-To: <4D519DC8.9070908@candelatech.com>

On 02/08/2011 02:47 PM, Ben Greear wrote:
> On 02/08/2011 11:29 AM, Jeff Mitchell wrote:
>> Hello,
>>
>> I have a bridge to various interfaces. There is an IP address on the
>> bridge, and hosts on the interfaces connected to the bridge use the
>> bridge's IP address as a gateway. STP is off and the forwarding delay is
>> set to 0.
>>
>> This has been working fine, however, today I needed to change around
>> some IPv6 addresses on the connected hosts. I made the IPv6 changes and
>> rebooted those boxes, only to find that suddenly no traffic -- IPv4 *or*
>> IPv6 -- was passing through the bridge.
>>
>> When I pulled up tshark to see what was going on, traffic suddenly
>> started flowing again. And even as I type this, as long as tshark is
>> running on that interface (no matter what the capture filter is),
>> traffic is flowing. The moment I stop tshark from running, traffic
>> stops. IOW, the bridge is only passing traffic while in promiscuous mode.
>>
>> I didn't change the IP address on the bridge itself. As far as I can
>> tell I didn't do anything odd whatsoever. But I have no idea what's
>> causing this and I'd really like to not reboot the box if at all possible.
>>
>> Does anyone have any idea what might be causing this and/or how to
>> troubleshoot this?
>
> What kernel version?
>
> And, you are sniffing the physical interface, or the bridge?
>
> Maybe send us output of brctl show, and ifconfig -a?
>
> Promisc bit is sometimes hard to detect properly, so if you can, please
> post /sys/class/net/[iface-name]/flags
> If bit 0x100 is set, the NIC is actually promisc, regardless of what
> ifconfig -a shows.

I found other funky behavior (sendmsg denied when trying to ping via 
IPv6) and users had trouble accessing services on the box, so I already 
initiated a reboot of the box -- I need those services up. :-|

If it happens again I'll be sure to get you that info.

However, here's what I *can* provide:
2.6.36 kernel, and sniffing the bridge. (There's actually no physical 
interface on the bridge -- this is on purpose, to prevent any problems 
on the bridge from affecting the one physical interface on the box, and 
thus my ability to get in and fix things.)

--Jeff

      reply	other threads:[~2011-02-08 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 19:29 [Bridge] Bridge suddenly only passes traffic if in promiscuous mode Jeff Mitchell
2011-02-08 19:47 ` Ben Greear
2011-02-08 19:50   ` Jeff Mitchell [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=4D519E97.40706@ll.mit.edu \
    --to=jmitchell@ll.mit.edu \
    --cc=bridge@lists.linux-foundation.org \
    --cc=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.