Hide Forgot
Description of problem: Current RHEL6 kernel has no support for bridge based igmp snooping. Without this feature, multicast frames may not be received properly, leading to ipv6 errors, such as not generating SLAAC based ipv6 global addresses Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.configure a bridge br0 2.attach a physical interface to it that emits router advertisements 3.bring br0 up Actual results: no SLAAC ipv6 address generated Expected results: SLAAC ipv6 global address assigned to br0 based on router advert. Additional info: This is fixed upstream with the addition of these patches: 6e7cb8370760ec17e10098399822292def8d84f3 8ef2a9a59854994bace13b5c4f7edc2c8d4d124e 08b202b6726459626c73ecfa08fcdc8c3efc76c2
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3425798 brew build
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3428084 New build.. forgot to git add a file
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3429826 New buidl. more s390 specific errors.
Patch(es) available on kernel-2.6.32-168.el6
*** Bug 727040 has been marked as a duplicate of this bug. ***
(In reply to comment #13) > *** Bug 727040 has been marked as a duplicate of this bug. *** RHEL 6.2 beta has not fixed the IGMP snooping issue (BZ 727040) for MLD v1 while it does for IGMP v1 and v2. An upstream commit already has a fix: commit fc2af6c73fc9449cd5894a36bb76b8f8c0e49fd8 Version-Release number of selected component (if applicable): kernel-2.6.32-202.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1530.html