Blocking tens of thousands of IP's

[CJ Ess]

OVH and Hetzner CIDR lists from RIPE are huge because of all the tiny
subnets - however they compress down really well if you merge all the
adjacent networks, you end up with a few dozen entires each. Whatever set
of CIDRs you are putting in a set, always merge them unless you need to
know which specific range in your source list was hit, thats my advice.

My experience is that both OVH and Hetzner take abuse complaints seriously
and if you make the effort to contact them then they will either compel
their customers to respond to you or cut them off if they can't be
contacted. However when you get to the former eastern block countries and
onward that doesn't happen - maybe Google Translate is just really bad at
Indo-European languages, but I suspect its more cultural.


On Tue, Nov 8, 2016 at 6:15 PM, <lists at lazygranch.com> wrote:

> Is that 2.2 million CIDRs, or actual addresses?
>
> I use IPFW with tables for about 20k CIDRs. I don't see any significant
> server load. It seems to me nginx has a big enough task that it makes sense
> to offload the blocking to something that is more tightly integrated to the
> OS.
>
> At a bare minimum, block OVH and Hetzner. People bash the Russians and old
> Soviet block countries for hacking, but OVH and Hetzner are far worse.
>
>
>   Original Message
> From: mayak
> Sent: Tuesday, November 8, 2016 2:58 PM
> To: nginx at nginx.org
> Reply To: nginx at nginx.org
> Subject: Re: Blocking tens of thousands of IP's
>
> On 11/08/2016 07:28 PM, Jonathan Vanasco wrote:
> > On Nov 4, 2016, at 5:43 AM, mex wrote:
> >
> >> we do a similar thing but keep a counter within nginx (lua_shared_dict
> FTW)
> >> and export this stuff via /badass - location.
> >>
> >> although its not realtime we have a delay of 5 sec which is enough for
> us
> <snip>
> We are blocking 2.2 million addresses, however, we do it at the
> firewall/router (pfsense pfBlocker).
>
> Ultra fast.
>
> HTH
>
> Mayak
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20161118/0042a9b9/attachment.html>