this bug is still in the 12.04 LTS version of iptables - 1.4.12-1ubuntu5 is there anyway that you can port the fix down to 64bit 12.04 Precise LTS?
this bug is still in the 12.04 LTS version of iptables - 1.4.12-1ubuntu5 is there anyway that you can port the fix down to 64bit 12.04 Precise LTS?