http://qa.mandrakesoft.com/show_bug.cgi?id=2567
------- Additional Comments From [EMAIL PROTECTED] 2003-03-04 01:15 ------- Hi, I didn't explain correctly the problem, but the segfault is elsewhere (and easy to reproduce). Sorry :-S 1. iptables-save tells me: *nat :PREROUTING ACCEPT [28:1407] :POSTROUTING ACCEPT [0:0] :OUTPUT ACCEPT [9:706] -A POSTROUTING -o ppp0 -j MASQUERADE COMMIT 2. I save these rules (for example) in the file iprules.txt (using: iptables-save > iprules.txt) 3. I edit the file and remove the "*nat" line. 4. I do: iptables-restore < iprules.txt and then it segfault. Same thing when I use stdin and omit the "*nat" line. 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: UNCONFIRMED 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
