since iptables has been upgraded to 1.3.1, ipac-ng
*should* segfault. i did not test it on the newest
version of ipcop but i have seen it crash on my system
with ipcop-ng 1.31 and iptables 1.3.1
have found another problem. on my installation ipac-ng does
return always 0 for the counters. (after i applied the
iptables-1.3.1 patch)
the new added patch solves the problem.
don't know how the old ipac-ng ever could work correctly.
maybe the old iptables begun counting rules from 0 and the
new version counts from 1. (?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
patch which fixes segmentation fault of ipac-ng
Logged In: YES
user_id=317036
Alan has now included this patch in 1.5
Logged In: YES
user_id=1159983
have found another problem. on my installation ipac-ng does
return always 0 for the counters. (after i applied the
iptables-1.3.1 patch)
the new added patch solves the problem.
don't know how the old ipac-ng ever could work correctly.
maybe the old iptables begun counting rules from 0 and the
new version counts from 1. (?)
patch with additional fix
Logged In: YES
user_id=255494
Great !
works fine on my SuSE 9.3.
I just had to modify the lib_dir to /usr/lib64/iptables as i
run the 64bit Version on an opteron.
Thanks a lot.