On Mon, Sep 16, 2013 at 01:59:31PM -0400, Laurence J. Lane wrote: > What error? >
Unfortunatly, I didn't write down the exact error message. From memory, and because I serched the internet right after I had it, I can definitly state that the error had a line number that points to a COMMIT directive. It could be that the error message actually had the word COMMIT. Similar reports on the Internet are http://help.lockergnome.com/linux/iptables-restore-barfs-COMMIT--ftopict282705.html and http://ubuntuforums.org/showthread.php?t=1918528 . > How do you produce it? > My rules includes a rule with a LOG target. When my kernel configuration had # CONFIG_NETFILTER_XT_TARGET_LOG is not set Not sure what module, or builtin facility, CONFIG_NETFILTER_XT_TARGET_LOG produces. Perhaps, when it is set to CONFIG_NETFILTER_XT_TARGET_LOG=m, one would get the xt_LOG.ko module. Anyway, when I load such a rule manually, and # CONFIG_NETFILTER_XT_TARGET_LOG is not set , I get immediately the iptables: No chain/target/match by that name. message. Which is reasonble. When I tried to iptables-restore < a list of rules that includes a rule with a LOG target I got an error message about a line number that failed. The line with that line number had a COMMIT directive. > Why is there a stated limit of version 1.4.20 and lower? The limit is because 1.4.20 is the version I have installed right now. By the reports in the internet, which seem to be old, I assume this bug is found on older versions too. You are right that my assumptions about the versions this bug is in are not sufficiently proven. One might suspect that vesrions later then 1.4.20 might have this bug. And some versions older then 1.4.20 might not have it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
