https://bugzilla.redhat.com/show_bug.cgi?id=634736
--- Comment #44 from Laine Stump <laine(a)redhat.com> ---
After all these years of asking for the default of bridge filtering to be
"disabled" and the change being refused by the kernel maintainers, now the
filtering has been moved into a separate module that isn't loaded (by default)
when the bridge module is loaded, effectively making the default "disabled".
Yay!
I *think* this is in the kernel as of 3.17 (It definitely is in kernel
3.18.7-200.fc21, and appears to be in git prior to the tag "v3.17-rc4")
So again the problem has disappeared for our case, so we're happy, but the
general problem (as in the latest version of this bug's summary) is still
there. What is the proper action for this BZ then? Do we leave it around
(knowing that, based on the experience up to now, the general problem will
likely never be fixed), close it as WONTFIX, or close it with one or another of
the "resolved" reasons, since our particular problem has been fixed by the
addition of the new module?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=RAeNfi7MWs&a=cc_unsubscribe