An experienced network engineer can look at the issued IPv4 ranges on a PC and work out why they may be having issues accessing the internet / network resources / VPN etc.
And with IPv6 it would be no harder - and in many ways a lot easier - for a given level of familiarisation.
If I tell you that a client at a.b.c.237 is struggling to talk to a.b.c.243 with a subnet mask of 255.255.255.224 - how long does it take you to work out what the numbers mean ? OK, if you deal with it all day every day you carry the tables in your head to convert the decimal to binary - but with IPv6 you only have to remember at most 16 binary values from 0000 (0) to 1111 (f) and subnet calculations are a lot easier. And you only ever have to do one nibble of comparison as the split is explicit (as in writing a.b.c.237/27 - and in a well setup network you'll NEVER have to do any binary as the prefixes will all be on nibble boundaries.
So ... IPv4 means learning "strange" tables of decimal-hex-binary-subnet length conversions, IPv6 means just comparing numbers are written and AT MOST doing on nibble of hex-binary conversion. So obviously, IPv6 is so much more complicated
Biting the hand that feeds IT
