Differences

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

--- training:sanog33:d-dhcpv6pd [2019/01/15 08:10] – [Setting up the DHCPv6-PD pool] philip
+++ training:sanog33:d-dhcpv6pd [2019/01/15 08:54] (current) – [Testing] philip
@@ 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`.
+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 =====
-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?
 [[:training:sanog33:agenda| Back to Agenda page]]