Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
userdoc:tt_ipv6_ula_nptv6_config [2017/06/04 13:05]
abelbeck [IPv6 ULA / NPTv6 Configuration]
userdoc:tt_ipv6_ula_nptv6_config [2017/06/04 13:27] (current)
abelbeck [Example IPv6 ULA / NPTv6 Setup]
Line 81: Line 81:
 Click **Configure Plugin**, set ''​ENABLED=1''​ and ... Click **Configure Plugin**, set ''​ENABLED=1''​ and ...
  
-Define the global prefix, since were using dynamic DHCPv6 only specify the prefix length:+Define the global prefix, since we are using dynamic DHCPv6 only specify the prefix length:
  
   NET_PREFIX_TRANSLATION_GLOBAL_PREFIX="::/​60"​   NET_PREFIX_TRANSLATION_GLOBAL_PREFIX="::/​60"​
Line 97: Line 97:
  
 \\ \\
-!!Important ->!! Carving the ULA/48 into ULA/​64'​s that will result in a 1:1 mapping to a GUA/60 is important to understand. ​ In the example above we used ''​IPv6/​nn''​ entries of ''<​ula>:​1::​1/​64''​ and ''<​ula>:​2::​1/​64''​ (where ''<​ula>''​ is shorthand for ''​fd06:​d115:​91f1''​). For a ULA/60 the largest possible sequence is ''<​ula>:​0::​1/​64''​ to ''<​ula>:​f::​1/​64'',​ which are 16 possibilities,​ but be careful the first ''<​ula>:​0::​1/​64'' ​can'​t ​be used since that will conflict with the first "​Assign GUA Prefix",​ since they are indexed 0, 1, etc. .  If we had selected a second "​Assign GUA Prefix"​ (index 1) we would have to start the ''​IPv6/​nn''​ entries with ''<​ula>:​2::​1/​64''​ or higher, best to start a little higher.+!!Important ->!! Carving the ULA/48 into ULA/​64'​s that will result in a 1:1 mapping to a GUA/60 is important to understand. ​ In the example above we used ''​IPv6/​nn''​ entries of ''<​ula>:​1::​1/​64''​ and ''<​ula>:​2::​1/​64''​ (where ''<​ula>''​ is shorthand for ''​fd06:​d115:​91f1''​). For a ULA/60 the largest possible sequence is ''<​ula>:​0::​1/​64''​ to ''<​ula>:​f::​1/​64'',​ which are 16 possibilities,​ but be careful the first ''<​ula>:​0::​1/​64'' ​best not be used since that will share the same address space as the first "​Assign GUA Prefix",​ since they are indexed 0, 1, etc. .  If we had selected a second "​Assign GUA Prefix"​ (index 1) it would be best to start the ''​IPv6/​nn''​ entries with ''<​ula>:​2::​1/​64''​ or higher, best practice is to start a little higher.
  
 ^ Suggestion on how to manage your ULA's with a GUA/60 prefix: ^^^ ^ Suggestion on how to manage your ULA's with a GUA/60 prefix: ^^^