From: Ben Hutchings <ben@decadent.org.uk>
To: Noah Meyerhans <noahm@debian.org>
Cc: 625914@bugs.debian.org, netdev <netdev@vger.kernel.org>,
bridge@lists.linux-foundation.org
Subject: Re: Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
Date: Tue, 10 May 2011 03:38:44 +0100 [thread overview]
Message-ID: <1304995124.4065.157.camel@localhost> (raw)
In-Reply-To: <20110506201234.6297.70279.reportbug@ip6-localhost>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Fri, 2011-05-06 at 13:12 -0700, Noah Meyerhans wrote:
> Package: linux-2.6
> Version: 2.6.38-3
> Severity: normal
>
> Hi. I've got a system that hosts several kvm virtual hosts. The VMs
> access the network via tap devices bridged with a physical interface.
> After upgrading to linux-image-2.6.38-2-amd64_2.6.38-4, I noticed that
> the virtualhosts were not autoconfiguring their IPv6 interfaces.
> Debugging revealed that no multicast was passing over the bridge.
>
> The bridge configuration is:
> bridge name bridge id STP enabled interfaces
> br0 8000.0002e3080eb5 no eth1
> tap0
> tap1
> tap2
>
> If I attach tcpdump to br0, I can see multicast (e.g. IPv6 Neighbor
> Solicitation) packets. However, if I attach tcpdump to eth1, I do not
> see multicast packets sourced from one of the VMs.
>
> Downgrading to 2.6.38-3 solves the problem.
This is pretty weird. Debian version 2.6.38-3 has a few bridging
changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
would cause this.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-05-10 2:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110506201234.6297.70279.reportbug@ip6-localhost>
2011-05-10 2:38 ` Ben Hutchings [this message]
2011-05-10 3:15 ` Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4 Stephen Hemminger
2011-05-10 4:38 ` Noah Meyerhans
2011-05-10 12:42 ` Ben Hutchings
2011-05-10 12:55 ` Yann Dupont
2011-05-10 18:05 ` Noah Meyerhans
2011-05-10 22:11 ` [Bridge] " Stephen Hemminger
2011-05-10 23:35 ` Noah Meyerhans
2011-05-12 22:59 ` David Miller
2011-05-12 23:28 ` Stephen Hemminger
2011-05-12 23:43 ` Stephen Hemminger
2011-05-13 5:03 ` Noah Meyerhans
2011-05-13 18:03 ` Stephen Hemminger
2011-05-13 19:53 ` [PATCH] bridge: fix forwarding of IPv6 Stephen Hemminger
2011-05-13 20:00 ` Eric Dumazet
2011-05-13 20:02 ` David Miller
2011-05-13 20:05 ` Eric Dumazet
2011-05-13 20:24 ` [Bridge] " Stephen Hemminger
2011-05-13 20:03 ` David Miller
2011-05-13 21:00 ` Noah Meyerhans
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=1304995124.4065.157.camel@localhost \
--to=ben@decadent.org.uk \
--cc=625914@bugs.debian.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=noahm@debian.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;
as well as URLs for NNTP newsgroup(s).