netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Guntsche <mike@it-loops.com>
To: xu@gibson.comsick.at
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: [BUG] bd4265fe36 bridge: Only flood unreg groups... breaks DHCP setup
Date: Tue, 5 Jul 2011 20:43:40 +0200	[thread overview]
Message-ID: <20110705204200@it-loops.com> (raw)

Hello,

After updating from 3.0.0-rc5 to rc6 I noticed that my cellphone was no
longer able to get an address assigned from my DHCP server. While trying
to figure out the problem I noticed that tracing with tcpdump made it
work again.

The setup I have here is the following:
PPC embedded board where the wired NIC and the wlan NIC are in a bridge.
Dnsmasq is listening on the Bridge device itself.

Looking at the changes between rc5 and rc6 I noticed commit

 bd4265fe365c0f3945d: bridge: Only flood unregistered groups to routers

For testing purposes I reverted it and the cellphone immediately got an
address even without running tcpdump. Now apparently the commit states
that the user can always force flooding behaviour to any given port by
marking it as a router but I did not find any documentation how to do
that.

Now my question? Is it "normal" that this change breaks my setup here
and if it is expected how can I force my ports to the old behaviour
without reverting the commit.

Thank you very much in advance,
Michael 

             reply	other threads:[~2011-07-05 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 18:43 Michael Guntsche [this message]
2011-07-05 23:58 ` [BUG] bd4265fe36 bridge: Only flood unreg groups... breaks DHCP setup Herbert Xu
2011-07-06  1:40   ` David Miller
2011-07-06  5:06     ` Stephen Hemminger
2011-07-06  5:08       ` Herbert Xu
2011-07-06  5:35         ` Stephen Hemminger
2011-07-06  5:45           ` Herbert Xu
2011-07-06  7:57   ` Michael Guntsche

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=20110705204200@it-loops.com \
    --to=mike@it-loops.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=xu@gibson.comsick.at \
    /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).