In Figure 1, the show ipv6 protocols command does not provide the same amount of information as its IPv4 counterpart. However, it does confirm the following parameters:
1. That RIPng routing is configured and running on router R1.
2. The interfaces configured with RIPng.
The show ipv6 route command displays the routes installed in the routing table as shown in Figure 2. The output confirms that R1 now knows about the highlighted RIPng networks.
Notice that the R2 LAN is advertised as two hops away. This is because there is a difference in the way RIPv2 and RIPng calculate the hop counts. With RIPv2 (and RIPv1), the metric to the R2 LAN would be one hop. This is because the metric (hop count) that is displayed in the IPv4 routing table is the number of hops required to reach the remote network (counting the next-hop router as the first hop). In RIPng, the sending router already considers itself to be one hop away; therefore, R2 advertises its LAN with a metric of 1. When R1 receives the update, it adds another hop count of 1 to the metric. Therefore, R1 considers the R2 LAN to be two hops away. Similarly it considers the R3 LAN to be three hops away.
Appending the rip keyword to the command as shown in Figure 3 only lists RIPng networks.
Use the Syntax Checker in Figure 4 to verify the R2 and R3.