Package: iptables Version: 1.4.14-2 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
After the upgrade from 1.4.13-1.1 to 1.4.14-2 loading LOG rules with iptables-restore is broken. Loading a rule like -A INPUT -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "foo" I end up with -A INPUT -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "--l" Changing the length of the log prefix gives me more or less "--log-prefix" as log prefix. So I suspect that --log-prefix and the argument are mixed up at some place. Using iptables to add the rule works fine, though. Kind regards - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (650, 'unstable'), (601, 'testing'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iptables depends on: ii libc6 2.13-33 ii libnfnetlink0 1.0.0-1 iptables recommends no packages. iptables suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP5CzhAAoJEGny/FFupxmTFbsP/R8vIpXTDqySrTJnt1DS8Cm6 XwZ/gypCaUWTBt9TvbKpbNLDWX8IiqHrCUdhz8UVWRY1hfU2/Ng3lTt4U/oToMI3 EAXodVxUy2FgMy1xP2rqjuOUBOCXQz58WjnoJPv+4bLW3Wvgqsje2Y8zQrqTewI+ zPhKl5+IhUFCQKsdcoUW6cmlGCxN5UDytmE3WuXlSbH36tq+c1eONCcRXfj1HhE8 ZIOyxWJOb5jIJ9MZO0eqvoYz0yWsg+VnZHWhhqaKHTe/AiQk6Z3NONKAlofIANla APCWyQ0A6B33fd4frxQ7Ec0QMYnMlRX7en/E4g/tnocXs+Sesk/F3OFJQTGmWYy2 9Ncp2dwIJVLwDuimsqvMUPeERWItEjoxkxlm2uppniKgm8opUejl61oiGxjNTawI wbdNY2XzR4dNr+88+7ubkRk7XjJfEa/02TbMvLWQyZ/lxj2mS2Bt9TDjbF/NFvhV ZjERissyRCQa3Uz5bUC/4GdAayjy3/uboRir4JTxMvCaWhejuPdgX10/RhfyEH1R ueLU7/OrzydiIQWAiY1Q5BDauexx3W0XRJgI7uTqUqnz8fLEUTpWm8Ufp6VTmac6 kzzT6mQuuBUJQssQ9XpwSBDEmikYFsyhBYnVgeD8LqcuIwzI5c+aie04iR8m4GtG 8kO4FbbcCgW9xYOJOxAA =cqIr -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
