4 ms·
As the article describes, it doesn't help, because the traffic originates from millions of unique residential IPs across hundreds of ASNs and countries.
by mzajc 1mo ago
As the article describes, it doesn't help, because the traffic originates from millions of unique residential IPs across hundreds of ASNs and countries.
- inigyou 1mo agoSo?
- VladVladikoff 1mo agoHave you tried blocking a million IPs before? Fail2ban gets pretty shaky at even 200,000 The AI crawler traffic I’ve seen sends one request per ip and seemingly has an infinite pool of residential IPs. You can’t block the ASNs becuase you also block honest clients. IP blocks are the wrong solution. And because I’m being negative I’ll also be constructive, IMHO the correct solution for fighting residential proxy crawlers is using RTT diffs this is one example https://github.com/Sakura-sx/Aroma https://github.com/Sakura-sx/Aroma
- pmlnr 1mo agoFail2ban becomes a serious bottleneck at significant traffic. I've replaced it with a shell script and direct pf commands that run every few minutes.
- virgoerns 1mo agoDo you mind sharing your script? I also noticed that fail2ban currently eats ~25% of CPU and started thinking if it's even worth running at this point
- pmlnr 1mo agohttps://petermolnar.net/article/asn-blocking-freebsd-pf-nginx/index.html https://petermolnar.net/article/asn-blocking-freebsd-pf-ngin... It's not the most sophisticated thing.
- left-struck 1mo agoRead the article, it will tell you why it won’t work.