I 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, t…
IPv4 Turf War
31–40 of 51 posts
Re: IPv4 Turf War
#32This 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
#33Re: IPv4 Turf War
#34I feel like this is a good time to plug Bot Net as a Service vendors like https://brightdata.com/
[0] https://spur.us/2020/08/residential-proxies-the-legal-botnet...
Re: IPv4 Turf War
#35I 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, t…
Basically I did a 1&2 combo. I run a small anti-bot service for a few friends sites and started redirecting a particularly aggressive scraper to the claim URL.
Re: IPv4 Turf War
#36https://youtu.be/bT8CRi9k4bo I like the test claim from localhost :).
Not for long though: https://www.ietf.org/archive/id/draft-schoen-intarea-unicast...
Some of space they are after, like 240/4, was always just "reserved" and you won't find as much resistance against it as reserved things are intended for exactly this kind of proposal. They just need to convince folks it's reasonably likely to be the best use of the space, overriding any significant unauthorized usage or alternative proposals as being less valid a use case, and it could be reasonably done. Real world implementation of the change might be a different story but they could at least get consensus that it's the intended use going forward.
Other spaces like 127/8 were actually assigned for use in the wild not just reserved for future use and despite 127.0.0.1 being most common address the others in the assigned space were definitely actually in use as well past the /16 they wish to preserve. This is especially in more networking infra focused contexts which are the things that would need to change most universally for this proposal to work. It's unlikely such a breaking standards change would get any consensus i.e. IMO that proposal is likely to never leave draft status.
David Täht, who was one of the authors of that draft, even holds regrets on the 127/8 proposal as it has caused the project to receive a lot of negative focus https://github.com/schoen/unicast-extensions/issues/16 and they have since let that draft proposal expire which is why your link is to an archived copy.
Re: IPv4 Turf War
#37I have hard time understanding how mikedamm@twitter claimed so many /8.
Re: IPv4 Turf War
#38I 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, t…
Re: IPv4 Turf War
#39[0]: https://redbean.dev
Re: IPv4 Turf War
#40I 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, t…
I do wonder what an IPv6 version of this would look like, but how it'd work, and how active it'd be.