Hacker News Reader

Comment by zhdc1 | Hacker News Reader

This. It’s ugly.

All of talk about the technical merits or demerits misses the point. I can spout of a dozen or more memorized IPv4 addresses. IPv6? Good luck.

View on HN

There's nothing stopping you from using memorable ULA prefixes on your LAN [0] and requiring the use of DHCPv6 for addressing so that each host gets a host part that is easy to remember. Hand-selecting your ULA prefix abandons the collision-resistance that you get from using The Technique to generate one, but if that's something you don't care about, then it's something you don't care about.

Plus, manual address assignment is just as viable in an IPv6 world as it is in IPv4.

[0] fd00::/64 is quite easy to remember, as are fd00::1 and similar.

Another option for simplicity in dual stack is to assign visually similar addresses:

    - ipv4: 192.168.0.42
    - ipv6: prefix:192:168:0:42

I only do this for static/server machines, configuring Linux with a fixed ipv4, and append the fixed ipv6 host to the Router Advertisement prefix.

If I hadn't put my long-running machines' -er- ULA-derived [0] SLAAC addresses into my local DNS ages ago, I'd either do exactly that, or slice off the "redundant" parts of the IPv4 address off, so that I could choose to assign sixteen additional bits of addresses to each host. That is:

  - ipv6: prefix:192:168:0:42

would become

  - ipv6: prefix::0:42:[0-ffff]

[0] I'm really not sure how to succinctly say "The autonomously-configured addresses on my LAN's ULA prefix".

Reply on news.ycombinator.com