Setup Dual Stack with NAT on v4
-
Again I hear you… So? Read https://tools.ietf.org/html/rfc7404
It clearly goes over the advantages and disadvantages to doing it that way.. There are many ways to skin a cat, I don't like skinning the cat that way because it has issues that I would rather not deal with...
Its not like you have to worry about running out of space by using up a /64 for your transit..
Unless you specifically configure using otherwise, you will normally be using link local. It happens with pfSense and it happens with routing protocols such as OSPF. The only purpose of the interface IP address in routing is to determine which link is used. When you look through the routing table, you will see the IP address will resolve to an interface, which is how routing takes place.
Now, there is nothing wrong with assigning a routeable address to an interface, for things like remote managment, ping, traceroute etc., but it normally will not have any purpose in the routing function.
-
Again I hear you… So? Read https://tools.ietf.org/html/rfc7404
I just did. That article points out why you'd need a routeable address for management purposes, not routing. Given that any interface that has a routeable address would also have a link local address (even my OpenVPN tunnel has a link local address), it's not an either/or situation. Use a routeable address for management and link local for routing. Regardless, a routeable address is not necessary for routing in IPv6. Incidentally, some of the things in that article might make a case for using ULA and not global addresses. ULA provides a routeable address that's not exposed externally.
