Helo,
we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615
The man pages say: recent is supported.
CentOS 6: is OK
Knows anyone more?
Best regards Helmut Drodofsky
On 11/09/2012 02:07 PM, Helmut Drodofsky wrote:
Helo,
we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615
The man pages say: recent is supported.
CentOS 6: is OK
Knows anyone more?
Error != unsupported
Check dmesg if it contains any hints on what iptables doesn't like about that command.
Regards, Dennis
On Fri, 2012-11-09 at 18:10 +0100, Dennis Jacobfeuerborn wrote:
On 11/09/2012 02:07 PM, Helmut Drodofsky wrote:
Helo,
we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615
Hello,
We're using 'recent' on CentOS 5.8 with no problems. The only difference I can see with your rule above is that you specify '-p tcp', whereas we have '-m tcp -p tcp'.
John.