[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1304995124.4065.157.camel@localhost>
Date: Tue, 10 May 2011 03:38:44 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Noah Meyerhans <noahm@...ian.org>
Cc: 625914@...s.debian.org, netdev <netdev@...r.kernel.org>,
bridge@...ts.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
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.
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists