4 ms·
> The GP was talking about running a purely v6 network, and pointing out that it wasn't yet feasible. Amusingly that's how mobile/smartphones are supposedly ru
by throw0101a 7y ago
> The GP was talking about running a purely v6 network, and pointing out that it wasn't yet feasible.
Amusingly that's how mobile/smartphones are supposedly run: the devices get IPv6-only, and if they need to hit an IPv4-only address they are CGNATed.
* https://www.internetsociety.org/resources/deploy360/2014/case-study-t-mobile-us-goes-ipv6-only-using-464xlat/ https://www.internetsociety.org/resources/deploy360/2014/cas...
* https://blogs.akamai.com/2016/06/preparing-for-ipv6-only-mobile-networks-why-and-how.html https://blogs.akamai.com/2016/06/preparing-for-ipv6-only-mob...
- exhilaration 7y agoAh, so that explains it. I just switched from Sprint (which always gave me an IPv4 address) to T-Mobile (which gives me an IPv6 address).
- jaywalk 7y agoMy Verizon iPhone has both a public IPv4 address and a public IPv6 address. They certainly could be using CGNAT, but that seems like a weird way to do it.
- throw0101a 7y ago> My Verizon iPhone has both a public IPv4 address and a public IPv6 address. How are you able to tell with IPv4? You cannot run ifconfig on an iPhone, so how are you determining that?
- wPfMiPmvaXQxERm 7y agoReally? My Verizon Android gets RFC6598 space.
- jaywalk 7y agoHoly cow, I don't know how I was never aware of RFC6598. When I saw the address starting with 100, I simply assumed it was an actual routable IP.