Hello. I have a system where iptables rules still work after being flushed. Yes, I know this will sound as an "X-File" or "The Twilight Zone", but that's exactly what happens. I've reported this problem to Debian here: http://bugs.debian.org/780494 Unfortunately, I can only reproduce it on a server used by many people, so I can't make a lot of experiments there. The system is running Debian jessie, with Linux 3.16.7 and iptables 1.4.21 (and also systemd, in case it matters). Simple questions: * Is there any kind of "version coupling" between Linux and iptables? (Say, "your kernel is too old / too new for the iptables version you are using") If so: How am I supposed to know if iptables does not complain? * Is there a reason why "iptables -L -n" could not be showing the *real* tables being used? * Any known bug (already fixed in the latest version) in Linux 3.16.7 or iptables 1.4.21 that may be the reason for this strange behaviour? Thanks. -- 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
