linux bridge problem

linux bridge problem

[Metuki Sabhe]

CC'ing netdev too:


 Hello,

 When I add interfaces to the bridge *after* I have "tcpdump -n -i br0"
 running on the bridge,
 my tcpdump don't see any communication. If I kill tcpdump and
 re-execute it *after* I added
 the interface to the bridge, it works just fine.

 The same behavior happens with my DHCP server (which listens only on
 my bridge interface);
 I need to re-execute (reset) it after I add the interface to the bridge.

 Is that normal ?

 Why does it happen ?

 What should I do ?

 It's a little awkward to reset my DHCP server every time I add a new
 interface to the bridge..

 Thanks,
 Sabhe

Re: linux bridge problem

[Mark Smith]

On Sat, 23 Jan 2010 16:41:40 +0200
Metuki Sabhe <sabhe.metuki@gmail.com> wrote:

> CC'ing netdev too:
> 
> 
>  Hello,
> 
>  When I add interfaces to the bridge *after* I have "tcpdump -n -i br0"
>  running on the bridge,
>  my tcpdump don't see any communication. If I kill tcpdump and
>  re-execute it *after* I added
>  the interface to the bridge, it works just fine.
> 

How long are you waiting? Make sure you're not encountering the default
forwarding delay of 20 seconds You can change that value to zero using

brctl setfd br0 0

which brings new interfaces into forwarding state immediately, rather
than going through the listening and/or learning states.

>  The same behavior happens with my DHCP server (which listens only on
>  my bridge interface);
>  I need to re-execute (reset) it after I add the interface to the bridge.
> 
>  Is that normal ?
> 
>  Why does it happen ?
> 
>  What should I do ?
> 
>  It's a little awkward to reset my DHCP server every time I add a new
>  interface to the bridge..
> 
>  Thanks,
>  Sabhe
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: linux bridge problem

[Metuki Sabhe]

Hi Mark,

On Sun, Jan 24, 2010 at 12:53 AM, Mark Smith
<lk-netdev@lk-netdev.nosense.org> wrote:
> brctl setfd br0 0

yep, that was it! thanks! unfortunately for me i found the culprit
soon after I send the mail. should have sent earlier to save me hours
of debugging :)

thank you,
sabhe