> Error 1005
> The owner of this website (www.bleepingcomputer.com) has banned the autonomous system number (ASN) your IP address is in (xxxxx) from accessing this website.
https://protonvpn.com/blog/apple-ios-vulnerability-disclosur...
Update: By vps i mean ip from digitalocean,linode, vultr etc.
Due to the fact that the Tor project provides a variety of lookup tools to determine whether an IP is an exit node -- including a DNS-based lookup -- it's trivial to block Tor users.
> Tor doesn’t have a static number of exit nodes and due to the variable nature of the network it’s difficult to block.
https://support.cloudflare.com/hc/en-us/articles/203306930-U...
And yes, there could be blocking by ranges.
And while I doubt that Tor would ever do it, one could use residential IPs via "free" smartphone apps. Some VPN services may be doing that.
No one could not use residential IPs that way.
But I don't see anything in https://trac.torproject.org/projects/tor/ticket/26646 about listing the IPv6 addresses. And using random addresses from multiple /48, that'd be an extremely long list.
I was wrong about not reusing IPv6. But even so, using the same IPv6 would be very rare, given the number available.
You say that no one could use residential IPs that way. But I know for a fact that it's already being done. For example, see https://luminati.io/proxy-networks/residential-ips.
https://metrics.torproject.org/rs.html#search/2001:
I see 377 starting with 2001:.
Handful of blocked ranges yes...
It's obvious that this isn't a goal of Tor.
But blocking has become so common that user pressure to prevent it can no longer be ignored. If they don't act, they risk being replaced.
I typically get around it by routing a VPN service, or a private VPN, through Tor. That also enables apps that require UDP. There is the risk of deanonymization, if VPN connections last too long and pin Tor circuits. Or if users don't adequately anonymize payment for VPN services or VPS used for private VPNs.
I started playing with a set of bash scripts that creates multiple VPN connections, with each using a different Tor circuit, and tests them. It periodically switches from one to another, and kills the old one. So both Tor circuit and VPN exit IPv4 change periodically. A script ongoingly starts and tests new VPN connections, to maintain availability. It's basically a crude hack of Tor's approach to circuit management.