From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 99081] New: Bridge multicast snooping breaks ICMPv6
Date: Thu, 28 May 2015 07:35:39 -0700 [thread overview]
Message-ID: <20150528073539.2619267a@urahara> (raw)
Begin forwarded message:
Date: Thu, 28 May 2015 10:34:55 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 99081] New: Bridge multicast snooping breaks ICMPv6
https://bugzilla.kernel.org/show_bug.cgi?id=99081
Bug ID: 99081
Summary: Bridge multicast snooping breaks ICMPv6
Product: Networking
Version: 2.5
Kernel Version: 4.0.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: sgunderson@bigfoot.com
Regression: No
Hi,
I've seen this reported many times around the net, with no definite solution;
since I got hit by it again and now used the latest kernel, I thought the best
place would be the kernel Bugzilla.
I have a bridge br0 with eth0 on it, and then some tap devices from KVM guests.
In this situation, by default, I don't have IPv6. I can't ping anything because
ND fails. I've seen this over multiple kernel versions for years, so I'm fairly
certain this is not something about my specific setup.
The common workaround is:
echo 0 > /sys/devices/virtual/net/br0/bridge/multicast_snooping
which immediately makes IPv6 work well again.
IPv6 unicast is unaffected; only multicast (ie., ND) seems to have the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-05-28 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150528073539.2619267a@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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