Re: [Bridge] [PATCH] bridge: fix forwarding of IPv6

2011-05-16 Thread Noah Meyerhans
IPV6 packet. > > Reported-by: Noah Meyerhans > Signed-off-by: Stephen Hemminger > > --- > Patch against net-next-2.6 but must be applied to net-2.6 > and stable as well > > --- a/net/bridge/br_netfilter.c 2011-05-13 12:37:30.289646958 -0700 > +++ b/net/br

Re: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4

2011-05-12 Thread Noah Meyerhans
On Thu, May 12, 2011 at 04:43:22PM -0700, Stephen Hemminger wrote: > > > There were two more follow on commits in stable related to this. > > > I recommend merging 2.6.38.6 which includes these. > > > > The problem still exists in the current 2.6.38.6. Backing out 5f1c356a > > still solves the pr

Re: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4

2011-05-10 Thread Noah Meyerhans
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote: > There were two more follow on commits in stable related to this. > I recommend merging 2.6.38.6 which includes these. The problem still exists in the current 2.6.38.6. Backing out 5f1c356a still solves the problem there. I have

Re: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4

2011-05-10 Thread Noah Meyerhans
On Tue, May 10, 2011 at 01:42:49PM +0100, Ben Hutchings wrote: > > > 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. > > > > I have apparently filed the bug against the wrong ve

Re: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4

2011-05-10 Thread Noah Meyerhans
On Tue, May 10, 2011 at 03:38:44AM +0100, Ben Hutchings wrote: > 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. I have apparently filed the bug against the wrong version of Debian's ke