2
In IPv4 people often use subnets like 10.0.0.0
(10.0.0.1
- 10.0.0.254
) or 192.168.0.0
Both of these are rather easy to remember. What is their alternative in IPv6? I know I can probably invent any possible subnet that comes to my mind, but I would rather use something more standard.
ISC-DHCP server uses 2001:db8:0:1::/64
in their example, but this address range seems to me quite complex and hard to remember.
Is it possible to use something very simple, such as a::0 - a::ffff
? What are some good examples easy to remember and also widely used?
Are you looking for addresses to assign to hosts in a network, or just to use in documentation/examples? – heavyd – 2015-05-18T16:26:56.610
1Memorability is one thing IPv4 sometimes had that IPv6 largely leaves in the past. The sooner one learns to stop hoping for IPv6 address memorability, the better. – Spiff – 2015-05-18T16:57:10.617
@heavyd I am looking for addresses to assign to hosts on a LAN – Petr – 2015-05-19T15:00:38.100
@Spiff what's wrong on IP adresses being easy to remember? Especially if it's just a LAN network where I should be technically able to use pretty much any free / useable address? Why would I want to prefer something that is hard to remember over something that is easy to remember? Especially for network services for which I need to remember IP address, like DNS server. – Petr – 2015-05-19T15:02:39.913
@Petr, in that case you should be assigning IP addresses based on the prefix your ISP assigns you. The last 64 bits of the IP can be whatever you want, but the first 64 are assigned by your ISP. – heavyd – 2015-05-19T15:05:03.010
@Petr There's nothing "wrong" with IPv6 addresses being easy to remember, it's just a v4-ism that doesn't really hold in v6; you're clinging to outdated notions instead of fully seeking IPv6 enlightenment :-) . As for DNS, DNS server addresses are provided in v6's Router Advertisements. You should never have to manually type them into a client machine, even when you're not using DHCPv6. – Spiff – 2015-05-19T16:00:08.100
1@Petr Wanting to have a non-public/non-routable prefix you use when setting up private LANs is also an outdated holdover from the days of IPv4 address scarcity. In the early 1990's, before IPv4 addresses became scarce, network admins were encouraged to get globally unique public routable subnets even when creating isolated LANs. With IPv6's mind-bogglingly-huge address space, we're back to those good old days. Even if you're setting up an isolated LAN, get a real IPv6 prefix for it (that is, if you need routers on it. If you don't need routers, just let it do link-local SLAAC). – Spiff – 2015-05-19T16:06:07.170