IPv4 is perfectly and objectively fine on internal networks. IPv6 is overkill and way too complicated for most.

IPv6 can be selectively applied to say, NAT addresses, but other than that, IPv4 is just fine and your statement is incorrect.

▲

throw0101c 2 hours ago | parent | next [-]

> IPv4 is perfectly and objectively fine on internal networks. IPv6 is overkill and way too complicated for most.

Unless there's a merger/acquisition and the two companies both use 10.0.0.0.

Most home networks use 192.168, and so you can't use that in corporate environments, because the WFH people who VPN in could then have routing snags between local and remote locations.

Also, in your VPN software be sure to perhaps not use 172 addresses (like my previous job did), as some of those ranges are used by Docker by default, and so you can cause issues for developers.

But other than that IPv4 RFC 1918 is not complicated at all…

▲

orangeboats 4 hours ago | parent | prev | next [-]

You can't selectively use IPv6 in the WAN and IPv4 in the LAN.

How would an IPv4 client send a packet to an IPv6 server? The IPv4 packet has only 4 bytes to spare for the destination address.

You can't.

Anything longer, even if it's just 1 bit, would require a new IP version.

▲

freeone3000 3 hours ago | parent [-]

You can run a 4to6 NAT, where specific v6 addresses (the ones you’re talking to) are aliased to reserved v4 addresses out of the PUA.

	▲	orangeboats 2 hours ago \| parent [-]
		I have seen people suggesting this before, but it's problematic for a few reasons: - If you are managing the 4to6 mappings manually, it's obviously not going to be scalable. Just to give people an idea, websites nowadays can connect to 10+ IPs in a single page due to CDN load balancing and stuff. - If you are handling the mappings automatically, such as by monitoring DNS queries and creating dynamic mappings based on that, the issues become more insidious: applications with hardcoded IP literals would fail without an obvious reason.

▲

growse 3 hours ago | parent | prev [-]

Alternatively, IPv4 simply does not scale effectively on the LAN, whereas IPv6 allows much simpler addressing and routing topologies. Simple = good.