Remix.run Logo
▲ georgyo 5 hours ago

This is all the bad parts of ipv6 with none of the good parts...

You still need to have routers, clients, and absolutely everything to understand the new scheme to use those new addresses.

▲charlieyu1 4 hours ago | parent [-]

Not using hex is a plus I guess?

▲growse 4 hours ago | parent | next [-]

You're welcome to not use hex. For either addressing scheme.

▲charlieyu1 29 minutes ago | parent | next [-]

IPv6 is 16 bytes, the person I replied to gives a 8 bytes scheme

▲bottled_poe 4 hours ago | parent | prev [-]

And vice-versa for decimal on ipv6 if desired, I guess?

▲throw0101c 4 hours ago | parent [-]

> And vice-versa for decimal on ipv6 if desired, I guess?

Or octal:

* https://networkingtoolbox.net/ip-address-convertor/represent...

▲bluGill 4 hours ago | parent | prev | next [-]

Computers use binary. Hex is a human convenience. For anyone in computers hex is much better than decimal for obvious reasons. For anybody not in computers hex makes no sense and I'd need weeks of math lectures (which they wouldn't do the homework for and thus fail) to explain it.

▲Sharlin 4 hours ago | parent | prev [-]

Honestly IPv4 addresses should always have been formatted in hex, like FF 00 00 69, with whatever delimiter. Would make it trivial to write directly as a 32-bit int, and parsing and formatting a string would also be cheaper. And you could have funny blocks like CAFE.0.0.

▲WorldMaker 3 hours ago | parent [-]

You can indeed make good use of those funny names in IPv6. If your /64 or /56 prefix is $prefix you can assign your coffee pot to $prefix::cafe or maybe keep it just fe80::cafe if you only want link local access to your coffee pot.