3 ms·

Who in their right mind is memorising IPv4 addresses, at least beyond the IP range used on their home network? Nobody remembers MAC addresses because nobody nee

Who in their right mind is memorising IPv4 addresses, at least beyond the IP range used on their home network? Nobody remembers MAC addresses because nobody needs to: IP and the upper layers hide that. If you don't want to adopt IPv6 because it would make remembering your IP addresses harder I'd say you have much more pressing issues to resolve first. I'd also argue that many people, me included, have simply stopped remembering phone numbers (and maybe addresses) now. I have some (my parents', etc) committed to long-term memory but there is no way I need or even try to remember new phone numbers I come across. My contacts list does it for me. IPv6 adoption is slow because a) it hasn't been essential so far, b) it's weird and different to IPv4 and if using it isn't essential, why bother? It's the technical equivalent to rewriting all your recipes from imperial to metric units, despite owning scales and measuring tools that still do both. (Note: I am a nerd and like playing with this stuff so I am mostly v6 where possible.)

CarelessExpert 6y ago
> Who in their right mind is memorising IPv4 addresses, at least beyond the IP range used on their home network? Hell, I don't even remember them on my home network. I have a server running a dozen VMs and I'll be damned if I can remember the IPs for all those services. DNS exists for a reason. Moreover, the only time I might be working with those raw IPs is with services using static IPs. But in that case my IPv6 addresses aren't actually that much more complicated. On the v4 side I might have: 192.168.1.122 And on the IPv6 side (where I have a /48 allocated) I might have: 2600:ABCD:XYZW::11
- cranekam 6y ago
  Yes, it's all easy. I have a /64 assigned to my LAN, an /80 assigned to each of my hosts for allocating IPs to containers, etc. I have DNS and a text file listing which blocks I have allocated out of the /48 my ISP gives me. It's not hard or substantially different to IPv4.

CarelessExpert 6y ago

> Who in their right mind is memorising IPv4 addresses, at least beyond the IP range used on their home network? Hell, I don't even remember them on my home network. I have a server running a dozen VMs and I'll be damned if I can remember the IPs for all those services. DNS exists for a reason. Moreover, the only time I might be working with those raw IPs is with services using static IPs. But in that case my IPv6 addresses aren't actually that much more complicated. On the v4 side I might have: 192.168.1.122 And on the IPv6 side (where I have a /48 allocated) I might have: 2600:ABCD:XYZW::11

cranekam 6y ago
Yes, it's all easy. I have a /64 assigned to my LAN, an /80 assigned to each of my hosts for allocating IPs to containers, etc. I have DNS and a text file listing which blocks I have allocated out of the /48 my ISP gives me. It's not hard or substantially different to IPv4.