The title pretty much explains everyrthing.
Since there is a huge amount of IPv6 addresess, couldn't every device just use a global unicast address? What is the practical use of unique local IPv6 addresses?
Thank you all in advance.
Network Engineering Stack Exchange is a question and answer site for network engineers. It only takes a minute to sign up.
Sign up to join this communityIs there any reason to use unique local IPv6 addreses in a production network?
You can use ULA for traffic that you never want to be able to be sent on the public Internet.
Since there is a huge amount of IPv6 addresess, couldn't every device just use a global unicast address? What is the practical use of unique local IPv6 addresses?
Yes, that is the point of IPv6 to restore the original IP end-to-end paradigm. Remember that IPv6 allows you to use multiple addresses on each interface, and you can mix the address types. You will have a Link-Local address, and you can add multiple Global and ULA addresses in different networks on the interface.
RFC 6724, Default Address Selection for Internet Protocol Version 6 (IPv6) defines an algorithm for source address selection. For example, if you have sensitive traffic that you send to a ULA address in your network, the source address should also be a ULA address you have defined on your interface. That will prevent the traffic from being able to be routed on the public Internet, protecting your sensitive information from accidental sending on the public Internet. You can also trust the source as it will obviously not be from the public Internet.
Since there is a huge amount of IPv6 addresess, couldn't every device just use a global unicast address? What is the practical use of unique local IPv6 addresses?
They could, but:
not all networks are in a position to obtain a global unicast prefix (as it's typically issued by your ISP), e.g. if you want to use IPv6 internally but your ISP doesn't support providing IPv6 access globally yet;
the global prefix is not always stable (sometimes the ISP refuses to provide a static prefix for "you didn't pay us enough" reasons) and you want stable addressing for your servers and stuff;
some networks have multiple prefixes from different ISPs, possibly coming and going (e.g. some basic load-balance or failover setups where BGP is not yet involved), and need one fixed prefix for internal communications.
(Both situations boil down to "renumbering is a pain".)