From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
To: Metuki Sabhe <sabhe.metuki@gmail.com>
Cc: bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: linux bridge problem
Date: Sun, 24 Jan 2010 09:23:33 +1030 [thread overview]
Message-ID: <20100124092333.230aa8eb@opy.nosense.org> (raw)
In-Reply-To: <549992e51001230641n2e40d2co31573386e258a5cb@mail.gmail.com>
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
next prev parent reply other threads:[~2010-01-23 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 14:41 linux bridge problem Metuki Sabhe
2010-01-23 22:53 ` Mark Smith [this message]
2010-01-24 15:11 ` Metuki Sabhe
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=20100124092333.230aa8eb@opy.nosense.org \
--to=lk-netdev@lk-netdev.nosense.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=sabhe.metuki@gmail.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;
as well as URLs for NNTP newsgroup(s).