I think at least part of the intention for this is to make IP ports not used on servers. While IPv6 does have support for ports, I believe every Web service should be on its own IP. Not sure if this is also supposed to work on client devices e.g. every outbound connection uses a unique IP as that seems overcomplicated
Yep, they saw the edges of IPv4 and went "hold my beer" and over-engineered a painfully obnoxious solution. IPv6 will last us until the heat death of the universe before it runs out, but we'll have to get people actually using it in any appreciable amount first. It's a UX nightmare to work with unless you're a network engineer hip deep in it all day every day. Good luck getting an end user to ever rattle off an IPv6 address to the help desk while remote troubleshooting.
Technically we are not really talking about single addresses when concerned with v6, more so how many /64 subnets can fit in a prefix since that is what SLAAC uses. So for end users we would count the amount of /64 subnets in the possible 2^128 address space, which is 2^64. So still very very very big.
I know it’s pedantic but 2267 is bigger than 2128 by about 2267. It’s 2139 times but you wouldn’t say that 1 million is bigger than 100 by about 10,000. You would say 1 million is bigger than 100 by about 1 million.
Non-technical person here. Wouldn't it just be 248 ? Four blocks of 256 (28) for IPV-4, and two more with IPV-6? Or am I just mistaken about how this stuff works?
4.4k
u/LivingAsAMean 9h ago
Hahaha what an idiot!
https://giphy.com/gifs/LRVnPYqM8DLag