3 ms·
IPv6 is not a requirement in all situations. At most enterprises need IPv6 at their edge to avoid traffic flowing through carrier grade nats. Internally private
by ec109685 9y ago
IPv6 is not a requirement in all situations. At most enterprises need IPv6 at their edge to avoid traffic flowing through carrier grade nats. Internally private IPv4, plus nats for egress are generally fine for most use cases.
- lmm 9y agoInternal IPv6 is much cleaner though, and less prone to failures (e.g. anyone VPNing in from a coffee shop that uses the same private IPv4 range will have a bad time). If you've already gone to the effort of getting IPv6 to the edge, surely at that point it's worth pushing it all the way through.
- bkor 9y agoNot just that, also in the case when a big company acquires/merges with another big company. The suggestion to have loads of servers on a private range such as e.g. 10.x.x.x is nice as it should be unique.. until this assumption breaks due to combining two networks together. It'll result in conflicts, discovery that lots of places had the IP address instead of a hostname, etc. It seems much saner to use IPv6.
- j_s 9y agoVPN from the same subnet simply doesn't work at all on Macs built-in VPN client, last time I looked into it. Windows built-in VPN client hasn't had a problem dealing with this for a long time.