IPv4 Turf War

Tonight I discovered I could create 128 m2.micros from my AWS account no questions asked. Very very worrying. Much happier with Hetzner with an initial limit of 25.

Re: IPv4 Turf War

#5

Post by clayloam » Sat, Sep 10, 2022, 9:18 PM UTC

Hey I made this!! Happy to see it getting attention. Feel free to ask me anything!

Re: IPv4 Turf War

#6

Post by clayloam » Sat, Sep 10, 2022, 9:20 PM UTC

cmeacham98 wrote: post #3

Cool idea, but please get an HTTPS cert - they're free!

I was planning on getting that set up, but people discovered it faster than anticipated :) I’ll do it soon

Re: IPv4 Turf War

#7

Post by PaoloBarbolini » Sat, Sep 10, 2022, 9:21 PM UTC

clayloam wrote: post #5

Hey I made this!! Happy to see it getting attention. Feel free to ask me anything!

Why are you doing a separate request for every /8? I feel like this would be the first thing that would kill the site, if it weren't for the fact you're on HTTP, the browser is talking HTTP/1.1, so it only does 6 concurrent requests per domain.

Re: IPv4 Turf War

#8

Post by clayloam » Sat, Sep 10, 2022, 9:23 PM UTC

PaoloBarbolini wrote: post #7

clayloam wrote: post #5

Hey I made this!! Happy to see it getting attention. Feel free to ask me anything!

Why are you doing a separate request for every /8? I feel like this would be the first thing that would kill the site, if it weren't for the fact you're on HTTP, the browser is talking HTTP/1.1, so it only does 6 concurrent requests per domain.

I wanted to see if the server could handle being slammed with requests like that :) but yeah collapsing it into one request would be a lot better. I’ll probably do that soon

Re: IPv4 Turf War

#9

Post by playingalong » Sat, Sep 10, 2022, 9:32 PM UTC

So some of them are public cloud, e.g. 3/8. And you can ran serverless there. Other option is to use some open proxy servers.

What other options do people have?

Re: IPv4 Turf War

#10

Post by jart » Sat, Sep 10, 2022, 9:35 PM UTC

clayloam wrote: post #8

PaoloBarbolini wrote: post #7

Earlier quoted context omitted.

Why are you doing a separate request for every /8? I feel like this would be the first thing that would kill the site, if it weren't for the fact you're on HTTP, the browser is talking HTTP/1.1, so it only does 6 concurrent requests per domain.

I wanted to see if the server could handle being slammed with requests like that :) but yeah collapsing it into one request would be a lot better. I’ll probably do that soon

In case anyone's wondering, I wrote the web server clayloam is using. It's called redbean. It started off as just my own hobby project last year, here on Hacker News, but it grew into something more and lots of people loved it enough to help. So it's very exciting to see it being used in production to handle hundreds of http messages per second. https://redbean.dev