Hi,
today I ran into a problem where several IPs where syn-flooding one of our
webservers. The first issue was that the conntrack table was filled up on
the firewall and I had to put a NOTRACK rule into the raw table to get that
"fixed". Once we got a better picture of the situation we blocked the
offending IPs and things wend back to normal on the web server.
My question is how do I handle this case in a more scalable fashion in the
future. I found the following rules on the net and they seem to do what is
needed (namely blocking IPs that create an excessive number of syn
connections):
iptables -A INPUT -m state --state NEW -p tcp -m tcp --syn \
-m recent --name synflood --set
iptables -A INPUT -m state --state NEW -p tcp -m tcp --syn \
-m recent --name synflood --update --seconds 1 --hitcount 30 -j DROP
What I'm wondering about is the "--state NEW" part. If I re-enable
connection tracking again for the above rules to work wouldn't these fill
up again and basically make these rules useless? Or can I essentially
remove the state module bits and just use the plain packets for this since
the syn flag is only used in establishing a new connection anyway which
makes the "--state NEW" bit not necessary?
Regards,
Dennis
--
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