|
| ▲ | orangeboats 3 hours ago | parent | next [-] |
| By being IPv6-only they are effectively making their users to preferentially connect over native IPv6 though. Personal anecdote, but once you have IPv6 setup properly (meaning your devices prefer IPv6 over IPv4) 70-80% of your internet traffic will be IPv6. The NAT64 is really just there for the holdouts. |
| |
| ▲ | ectospheno 2 hours ago | parent [-] | | I run dual stack at home with dns64/nat64. I average 50/50 traffic v4/v6. Web browsing gets skewed v6 but large file transfers and some streaming pushed it back to 50/50 overall. My family would revolt if I went v6 only so I'm not sure I'd say its just there for holdouts. Major annoyances include any old device and my hue bridge. |
|
|
| ▲ | cornholio 2 hours ago | parent | prev | next [-] |
| That's a bit like saying AC electricity was just a fancy way of delivering what customers really wanted, DC energy. I'm sure that DC customers used their Edison DC equipment for decades after the grid went AC only; but in the long run the newer, flexible, lower overhead system became the default for new equipment and the compatibility cludges were abandoned. |
| |
| ▲ | amelius an hour ago | parent [-] | | High voltage AC actually gives more overhead than the same voltage DC. |
|
|
| ▲ | nine_k 3 hours ago | parent | prev [-] |
| No; most sites I reach from the phone seem to be reached via IPv6. E.g. hitting whatismyip.org exposes an IPv6 (though mentions an IPv4 because they're trying to discover that, too).
Some sites do not support IPv6; for those indeed there's a XLAT464 service. |
| |
| ▲ | sgjohnson 2 hours ago | parent [-] | | 464XLAT is for dealing with IPv4 literal addresses in a v6 only network. Non-literals can be addressed with DNS64 & NAT64 |
|
