Forum Discussion
Google blocking search
The real fix for this is to transition to a true IPv6 network in which each user gets a unique IP address instead of using CGNAT, which assigns hundreds of users (or however many T-Mobile is doing) to a single public IPv4 address. To put it in perspective, there are about 3.7 billion public IPv4 addresses. However in a traditional sense, each device would need to have a single distinct IP address. With over 8 billion people on earth, that isn't practical. In the past, this was dealt with by using local addresses that were then handled through a single public address per network (which is why you can have a 192.168.1.1 on your network and so can your neighbor). From there, your router will take incoming data from the outside world and intelligently route it to the correct device in your home. This is the way it was for decades, where each individual subscriber would have a unique address. But due to IPv4 number exhaustion, T-Mobile and other ISPs have gone to a second level of routing in which they have an IPv4 address that is assigned to multiple subscribers and they act like the router in your home to send the data streams to the right subscriber (likely by using IPv6, interestingly enough). So T-Mobile can't get any more IPv4 addresses, as there aren't many left, so they are just expanding the number per public IP (conjecture on my part, but I'd wager it is pretty accurate). Thus, Google sees a ton of traffic, it triggers their protection system, and here we are. I fully expect this will expand to further sites as time goes on.
Contenido relacionado
- Hace 11 meses
- Hace 7 meses
- Hace 3 meses
- Hace 11 meses