Had some fun with this. I used fireprox[0] to grab a ton of AWS IPs, and some proxy vendors for some other random ranges. Sadly my ASN has only /24s in disparate ranges so it wouldn’t make a dent for most of them.
IPv4 Turf War
21–30 of 51 posts
Re: IPv4 Turf War
#22I considered testing out whether spoofing was blocked on Vultrs network, but too lazy.
Re: IPv4 Turf War
#23I considered testing out whether spoofing was blocked on Vultrs network, but too lazy.
Source spoofing wouldn't get you far enough into the connection to make the claim and BGP hijacking is prevented on Vultr (you have to file a ROA and update RPKI before they'll accept the advertisement).
Re: IPv4 Turf War
#24I feel like this is a good time to plug Bot Net as a Service vendors like https://brightdata.com/
Re: IPv4 Turf War
#25So 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?
Some more to add to the pile:
- Static IP blocks from their ISP (some still lease IPs for surprisingly cheap).
- Releasing/renewing their NAT boxe's DHCP release on carriers that don't pin assignments (usually these are in pools of /22 or 1024 addresses - though most would be in use at any given time and impossible to randomly get you should be able to get a couple dozen).
- Customers of ISPs that use CG-NAT (cheap wired) or NAT64 (some wireless providers), similar to the above just 1 translation layer deeper.
- IP space you control (that's how I have 23.0.0.0/8 for the moment)
- BGP hijacking IP space you want to control (though hopefully in the world of RPKI this is getting harder and harder to do)
Re: IPv4 Turf War
#26This got me wondering that, in practice, how hard would it be to spoof source IP in the internet? I assume it requires some controls on an Tier-1 ISP network (so that the the spoofed package would not be filtered by upstream)?
Though apparently it doesn’t help in this case because it’s HTTP/TCP which requires a handshake
Re: IPv4 Turf War
#27Re: IPv4 Turf War
#28I had an almost identical idea to this website a while ago but never acted on it, props to the dev.
Here is how you win the IPv4 games, in order of most to least effective:
1) Have a large online following that is willing to visit your claim link or a page where you can embed an iframe / img / etc that points to your claim link.
2) Pay to use someone else's (consensual) botnet by paying a residential proxy service, this is the approach I just used and it cost me a few dollars for access to a massive amount of distributed IPv4 space.
3) Abuse cloud / serverless offerings as far as they will go, unlikely to win more than a few blocks this way.
4) Own IPv4 space.
Other less ethical approaches: possibly exploit the system by sending a XFF header the developer forgot to block (probably just checking socket address so unlikely to work here), spin up a Vultr VPS in the same DC and probe for a way to connect with a local address, hijack BGP space, run your own botnet, I'm reminded of an old exploit in WordPress XMLRPC...
From what I can see the current rankings are just me and mike fighting for the same proxy space (the vote goes to the most recent visit per IP), and everyone else falls into buckets 3 & 4.
Re: IPv4 Turf War
#29Tonight 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.
No post body was provided.
Re: IPv4 Turf War
#30https://youtu.be/bT8CRi9k4bo I like the test claim from localhost :).
Not for long though:
https://www.ietf.org/archive/id/draft-schoen-intarea-unicast...