Now Blocking 56,037,235 IP Addresses, and Counting
cheapskatesguide.org
Now Blocking 56,037,235 IP Addresses, and Counting
1–10 of 62 posts
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#2Re: Now Blocking 56,037,235 IP Addresses, and Counting
#3> In case of a lot of rules, the use of the ngx_http_geo_module module variables is preferable.
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#4As long as you understand the limitations, ramifications, and futility in doing this, I have no problems with it as one of the many tactics to defend your footprint and de-noise your logs, etc.
It's a never ending endeavor and you will see the shifting attack sources from the baddies along with the games on stub blocks, prefix broker IP block swaps, and more.
Just know there is automation and horsepower into that entire attack infrastructure you can't possibly compete with but maybe you can mitigate with the limited time and resources you have and that will be enough to get you through.
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#5There's a significant mental leap here. "I block these IP to conserve my resources, therefore they belong to clueless or malicious organisations". It's wrong in both directions:
* I don't think Google, Bing and other crawlers are inherently malicious, and certainly not clueless. Search engines serve a very important role in the internet. Ditto archive.org, and probably dozens of other bots.
* IP based blocklists work well for honest bots (not malicious, or at least not illegal). Malicious bot operators just buy SIM cards and use regular mobile internet for the crawling (basically unblockable, because the IP may be renewed every day or every hour). And the really malicious actors use residential proxies, i.e. botnets that proxy traffic through normal users' computers. Anyway I wonder how many of those 56MM IP addresses are regular dynamically allocated consumer grade ISPs.
>1-5-2024
For the love of all that is holy, what is this date format.
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#6Re: Now Blocking 56,037,235 IP Addresses, and Counting
#7>It means that more than one percent of the IPv4 real estate on the Internet (and probably much more) is occupied by people and organizations who are either clueless or just do not care how much the rest of us are paying to keep our websites on line There's a significant mental leap here. "I block these IP to conserve my resources, therefore they belong to clueless or malicious organisations". It's wrong in both dire…
>For the love of all that is holy, what is this date format.
Most commonly used in the US. 'Cause we gotta show it like we say it. I think.
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#8Just do your own thing, learn from it, and repeat. That's all we can really want in our projects, on our limited lease on planet Earth. Kudos that you found something to work on.
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#9It seems to be a static site. Bots should cause only a neglible amount of traffic per month. My guess would be less than $1.
And aren't there free CDNs for static sites these days? I guess you can just push the whole frontent data (html+assets) into a public git repo, put it behind a github page with custom domain and call it a day?
Re: Now Blocking 56,037,235 IP Addresses, and Counting
#10"I imagine that if this article makes its way onto Hacker News, I will be criticized."
Edit: FWIW I think you’re fighting the good fight and I wish I could implement something similar at work, in where I constantly have bots trying to login to my corporate VPN.