https://bugzilla.redhat.com/show_bug.cgi?id=634736
--- Comment #35 from Laine Stump <laine(a)redhat.com> ---
Yay! I just tested this in an F21 vm which has no bridges in the system network
config, but does have a bridge created at a later time by libvirt - prior to
updating, these were the values of the bridge-nf-call-* tunables (in spite of
being set to 0 in /usr/lib/sysctl.d):
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
But after updating (and with no other modifications), I rebooted the vm and
found this:
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
So the changes you made *did* fix the original bug that I filed the BZ over -
thanks!
Will this BZ be moved from MODIFIED to CLOSED automatically when the relevant
packages make it into f21-updates, or does it need to be in ON_QA for that to
happen?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.