User Tools

Site Tools


training:sanog33:d-dhcpv6pd

Differences

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

Link to this comparison view

Next revision
Previous revision
training:sanog33:d-dhcpv6pd [2018/11/24 05:12] – created philiptraining:sanog33:d-dhcpv6pd [2019/01/15 19:54] (current) – [Testing] philip
Line 59: Line 59:
   ipv6 dhcp pool DHCPv6   ipv6 dhcp pool DHCPv6
    prefix-delegation pool dhcpv6-pool1 lifetime 1800 600    prefix-delegation pool dhcpv6-pool1 lifetime 1800 600
-   dns-server 2001:DB8:FFFF::1+   dns-server 2001:DB8:100::241
    domain-name lab.net    domain-name lab.net
   !   !
Line 68: Line 68:
   * `ipv6 dhcp pool DHCPv6` creates the DHCP pool configuration to be used on the interface connecting to customers.   * `ipv6 dhcp pool DHCPv6` creates the DHCP pool configuration to be used on the interface connecting to customers.
   * `prefix-delegation pool dhcpv6-pool1 lifetime 1800 600` says to use DHCPv6 Prefix Delegation, delegating prefixes from the pool called `dhcpv6-pool1` with a lifetime of `1800` seconds (30 minutes) and a preferred lifetime of `600` seconds (10 minutes).   * `prefix-delegation pool dhcpv6-pool1 lifetime 1800 600` says to use DHCPv6 Prefix Delegation, delegating prefixes from the pool called `dhcpv6-pool1` with a lifetime of `1800` seconds (30 minutes) and a preferred lifetime of `600` seconds (10 minutes).
-  * `dns-server` specifies a DNS resolver to use - this is just an example+  * `dns-server` specifies a DNS resolver to use - this is the lab DNS resolver
   * `domain-name` specifies the default domain-name for unqualified names - again this is just an example   * `domain-name` specifies the default domain-name for unqualified names - again this is just an example
  
Line 155: Line 155:
  
 Refer to the earlier discussion about the “general-prefix”. We have `2001:DB8:6:C000::/60` as the IPv6 subnet created by 6rd. Taking this and appending `::1:0:0:0:0` results in the first subnet to be allocated to the network - the `FastEthernet0/0` interface there is automatically assigned `2001:DB8:6:C001::/64`, with the IPv6 address on the interface being `2001:DB8:6:C001::1/64`. Refer to the earlier discussion about the “general-prefix”. We have `2001:DB8:6:C000::/60` as the IPv6 subnet created by 6rd. Taking this and appending `::1:0:0:0:0` results in the first subnet to be allocated to the network - the `FastEthernet0/0` interface there is automatically assigned `2001:DB8:6:C001::/64`, with the IPv6 address on the interface being `2001:DB8:6:C001::1/64`.
 +
 +Check the output of:
 +
 +  show ipv6 general-prefix
 +
 +and compare what you see here with what has been configured on the router's interfaces.
  
 ===== Testing ===== ===== Testing =====
  
-With the DHCPv6-PD now set up, trying some IPv4 and IPv6 traceroutes from the Customer router to the backbone Transit providers and out to the Internet. **Hint**: Use the Loopback interface as the source of your traceroutes and pings.+With the DHCPv6-PD now set up, try some IPv4 and IPv6 traceroutes from the Customer router to the backbone Transit providers and out to the Internet, for example, to 8.8.8.8 (IPv4) and 2001:4860:4860::8888 (IPv6).
  
-(Note that the lab doesn’t have IPv6 connectivity, but at least try IPv6 traceroutes into the Transit backbone and to other groups.)+(Note that if the lab doesn’t have IPv6 connectivity, try IPv6 traceroutes into the Transit backbone and to other groups.)
  
 What do you see? What do you see?
  
 [[:training:sanog33:agenda| Back to Agenda page]] [[:training:sanog33:agenda| Back to Agenda page]]
training/sanog33/d-dhcpv6pd.1542996724.txt.gz · Last modified: 2018/11/24 05:12 by philip