3 ms·
Sprint cannot currently translate IPV4 addresses (ex. 152.138.17.240) to an actual phone number Sprint may be able to translate IPV6 addresses (ex. 001:0db8:00
by gzer0 5y ago
Sprint cannot currently translate IPV4 addresses (ex. 152.138.17.240) to an actual phone number
Sprint may be able to translate IPV6 addresses (ex. 001:0db8:0000:0042:0000:8a2e:0370:7334) to a phone number.
Interesting, anyone know which aspect of the IPV6 protocol allows for this?
- itsthecourier 5y agothere are so many possible ipv6 public ips that absence of overlapping on assignation is doable and thus individual client determination
- bibaheu 5y agoProbably IPv4 is on CGNAT and Sprint doesn't keep the logs of the translation. On IPv6 there's no NAT, and there might be a deterministic relationship between subscription and IP
- glogla 5y agoThat, or they don't give devices IPv4 addresses at all and run 464XLAT - according to Wikipedia, quite a few telcos do it that way.
- keneda7 5y agoI believe you are correct. https://news.ycombinator.com/item?id=16440850 https://news.ycombinator.com/item?id=16440850
- p1mrx 5y ago464XLAT is a form of CGNAT. The main difference is whether the subscriber side uses an IPv6 or private IPv4 address, but on the internet side they are equivalent.