If you read the doco (like “man gai.conf”) you would be forgiven for thinking that the contents of /etc/gai.conf controlled source and destination address selection in IPv6. You would be wrong.
Category: Technical
-
Why Not NAT?
NAT came into existence because of IPv4 address scarcity. With IPv6, that reason disappears. So, if we no longer need to multiplex addresses, should we retain NAT?
-
Controlling IPv6 source address selection
In a previous article, I discussed how IPv6 source address selection worked. Normally it all Just Works, but there are several situations where you may want or need to control the address selection process. In this article, we’ll look at why you might want to control source address selection, and how you can do it.
-
IPv6 Source Address Selection – what, why, how
Source address selection must be very irritated; destination address selection gets all the press coverage.
This article will start to redress the balance, by talking about what source address selection is, why it is needed, and how it works. If you want the nitty-gritty, check out RFC 6724 (which obsoletes RFC 3484).
-
IPv6 ULA – what and how?
ULA (Unique Local Addresses, or Unique Local IPv6 Unicast Addresses to give them their full name) are IPv6’s equivalent of IPv4’s “private” addresses.
The idea is to append a random 40 bits to the reserved ULA prefix fd00::/8, thus building a /48 that you can call your own. You can use this /48 wherever and however you like, with the sole proviso that it must not be routed on the public Internet. The ULA space is defined in RFC4192 (http://tools.ietf.org/html/rfc4193).