2002::/16 prefix is used for 6to4, which requires the next 32 bits (after the 16 bit prefix) to be a global unicast IPv4 address.
You say it must be higher than
2002:0099:: which is probably because you haven't fully understood the hexadecimal part of the IPv6 address notation.
2002:0099:: would correspond to IPv4 address
0.255.255.255 is not a global unicast address either. So
2002:00ff:: would not work either.
Hosts on a LAN behind a 6to4 gateway don't need to know about 6to4. They can treat the 6to4 address assigned to them as if it was any other global unicast IPv6 address. As such, there are no requirement to reject
2002:0099:: as an invalid address, however since it never could be a valid address, it does make sense for an OS to reject it.
Using random 6to4 addresses for testing is definitely not recommended practice. If you want to experiment with IPv6, there are other ways to get addresses to experiment with:
- Construct a real 6to4 prefix by appending the IP assigned to you by your ISP to the 6to4 prefix. If your ISP had assigned
203.0.113.1 to you, you would convert each of the four octets to hexadecimal values
01 and your IPv6 prefix would be
- Get a tunnel through a tunnel provider.
- Get native IPv6 from your ISP.
- Use RFC 4193 addresses. With those the first octet must be
fd and the next five octets must be random. Your prefix could then be
fd2a:4b89:4d7d::/48. These can only be used locally, so if you configure such an address and no other IPv6 address there is a risk of software trying to communicate externally using this local IPv6 address instead of using IPv4.
The above options are not exclusive. It is perfectly valid to configure one (or more) of each kind of addresses. For testing and development it can be a good idea to assign multiple addresses in order to test interesting corner cases. For production environments you should be aware that many systems don't take source address into account when deciding which gateway to use, which can cause breakage if multiple addresses are used in a setting where routers are configured to drop packets with unexpected source IP.