I don't know about iptables, but you can limit port 80 and 443 with ipfw. I run mine at 10 per IP. I've had corporations behind NAT trigger lesser limits. My point being you don't have to parse the log (swatch). 



From: anoopalia...@gmail.com
Sent: August 1, 2017 8:26 PM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject: Re: nginx limit_req and limit_conn not working to prevent DoS attack

You can use an external tool to parse Nginx error log and block the IP in iptables/netfilter 

On Wed, Aug 2, 2017 at 7:43 AM, Phani Sreenivasa Prasad <nginx-fo...@forum.nginx.org> wrote:
I assume it would help dropping connections . since we are setting rate
limit per ip and any client IP which is suspicious by sending requests in
bulk(lets say 10000 connections/requests), it makes sense to not to accept
connections/requests from that IP.

Thoughts ??

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,275796,275798#msg-275798

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx



--
Anoop P Alias 

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Reply via email to