On Wednesday 2010-10-20 15:03, Maarten Vanraes wrote: >Op woensdag 20 oktober 2010 11:16:29 schreef Jan Engelhardt: >> On Wednesday 2010-10-20 10:25, Maarten Vanraes wrote: >> >> > ACCOUNT: Table publicnet found, but IP/netmask mismatch. IP/netmask >> >> > found: 194.0.234.0/255.255.255.0 >> >> > ACCOUNT: Table insert problem. Aborting >> > >> >this error message is due to a previous publicnet rule, and it can't seem >> >to find the matching network. even though it is the same one. (i suspect >> >it is due to network being 194.0.234.0/24 and the matcher is checking >> >194.0.234.0/255.255.255.0 ). also i suspect there is a another bug when >> >removing the rule that the matcher can't find the correct one (also due to >> >different netmask notations?) and thus not everything is removed which >> >means that i can't reinsert that one. >> >> Do you have a minimal testcase available? > > >machine is rebooted, no iptables yet, no modules loaded. > >[]# iptables -t mangle -I POSTROUTING -j ACCOUNT --addr 0.0.0.0/0 --tname self >iptables: Invalid argument. Run `dmesg' for more information. I fail to reproduce this in 64-bit and 32-compat environments. Since ACCOUNT.ko and x_tables.ko do output appropriate messages to dmesg along with returning EINVAL... I don't see much possibilities. One could be that you are using an overly old xtables-addons (<Â1.27) compat_xtables.ko with an overly new kernel (>= v2.6.35) - combined with having ignored the compile warnings/errors (when building from source, as DKMS unfortunately does). -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
