http://qa.mandrakesoft.com/show_bug.cgi?id=2567
------- Additional Comments From [EMAIL PROTECTED] 2003-03-05 12:31 ------- Hi, I have sent a bug report to bugzilla.netfilter.org. Their answer was: This bug has already been fixed with CVS version 1.23 of iptables-restore.c If you use a recent CVS snapshot, the bug is fixed. Otherwise you will have to wait for 1.2.8 Here is the diff (quite simple): http://cvs.netfilter.org/netfilter/userspace/iptables-restore.c.diff?r1=1.22&r2=1.23 Could it be applied ? Thanx. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: Hi, I create some rules that I list with iptables-save: # Generated by iptables-save v1.2.7a on Sat Mar 1 15:10:14 2003 *nat :PREROUTING ACCEPT [1670:81196] :POSTROUTING ACCEPT [56:5326] :OUTPUT ACCEPT [337:22639] -A POSTROUTING -o ppp0 -j MASQUERADE COMMIT When I run iptables-restore and write some rule using STDIN (for example :PREROUTING ACCEPT [1670:81196]), iptables-restore core dumps. gdb backtrace tells: (...) #0 0x0804ee83 in iptc_builtin () #1 0x0804a296 in main () #2 0x4003f7f7 in __libc_start_main () from /lib/i686/libc.so.6
