Re:Ask HN: How is DDoS protection implemented?
by bo1024 on Sunday May 13, 2018 @11:20PM
(#17062436)
For #2 -- how do you "kill" high frequency requests? By ignoring them?
[ Parent
| on HN ]
Re:Ask HN: How is DDoS protection implemented?
by colanderman on Sunday May 13, 2018 @11:41PM
(#17062507)
Yep. Add the source address (or some more specific yet easily computed identifier) to a table that is checked early in the network path (in hardware if possible).
Or, if you want to be fancy, "tarpit" them (complete TCP handshake and then ignore, forcing attacker to actually commit resources), but apparently that's of questionable value these days. [1]
Re:Ask HN: How is DDoS protection implemented?
by bo1024 on Monday May 14, 2018 @12:52AM
(#17062796)
Interesting, thanks.
Re:Ask HN: How is DDoS protection implemented?
by bArray on Monday May 14, 2018 @01:33AM
(#17062942)
In addition to @colanderman's suggestion I also do this on an application level - although not everyone will be able to do this.
Re:Ask HN: How is DDoS protection implemented?
by jmngomes on Monday May 14, 2018 @08:29AM
(#17064836)
Or by banning the source, especially repeat offenders.
I find that using a combination of nginx's limit_req and fail2ban over nginx logs is an easy measure that already goes a long way in handling basic types of DoS, like clients producing an abnormally high volume of requests.