Action: At R1#, issue show ip route static and show ipv6 route static.
Expected Terminal Output:
R1# show ip route static
S 10.1.1.0/24 [1/0] via 209.165.200.226
R1# show ipv6 route static
S 2001:DB8:CAFE:1::/64 [1/0]
via 2001:DB8:FEED:224::2
Criterion: Static routes to remote LAN are installed with Administrative Distance of 1 ([1/0]) via the correct R2 WAN next hop.
Test POS-02: End-to-End IPv4 Routing Reachability#
Action: From PC0 (192.168.10.2), ping PC2 (10.1.1.2).
Expected Terminal Output:
PC0> ping 10.1.1.2
Pinging 10.1.1.2 with 32 bytes of data:
Reply from 10.1.1.2: bytes=32 time=5ms TTL=126
Reply from 10.1.1.2: bytes=32 time=5ms TTL=126
Reply from 10.1.1.2: bytes=32 time=5ms TTL=126
Reply from 10.1.1.2: bytes=32 time=6ms TTL=126
Ping statistics for 10.1.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Criterion: 100% ICMP packet success across two router hops (TTL decremented by 2).
Test POS-03: End-to-End IPv6 Routing Reachability#
Action: From PC0, ping PC2 IPv6 address: ping 2001:db8:cafe:1::2.
Expected Terminal Output:
PC0> ping 2001:db8:cafe:1::2
Pinging 2001:db8:cafe:1::2 with 32 bytes of data:
Reply from 2001:db8:cafe:1::2: bytes=32 time=5ms TTL=126
Reply from 2001:db8:cafe:1::2: bytes=32 time=5ms TTL=126
Reply from 2001:db8:cafe:1::2: bytes=32 time=5ms TTL=126
Reply from 2001:db8:cafe:1::2: bytes=32 time=6ms TTL=126
Ping statistics for 2001:db8:cafe:1::2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Criterion: 100% IPv6 packet success across the dual-stack transit WAN link.
Test NEG-01: Asymmetric Routing / Missing Return Route#
Action: On R2, remove the IPv4 return route: no ip route 192.168.10.0 255.255.255.0 209.165.200.225. From PC0, ping PC2 (10.1.1.2).
Expected Terminal Output:
PC0> ping 10.1.1.2
Pinging 10.1.1.2 with 32 bytes of data:
Reply from 192.168.10.10: Destination host unreachable.
Reply from 192.168.10.10: Destination host unreachable.
Reply from 192.168.10.10: Destination host unreachable.
Reply from 192.168.10.10: Destination host unreachable.
Ping statistics for 10.1.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Criterion: R1 forwards the packet to R2, but R2 drops the return echo reply due to lack of a route back to 192.168.10.0/24. Proves that routing must be bidirectional.
Action: Configure static route pointing to an unconfigured next-hop: ip route 10.1.1.0 255.255.255.0 209.165.200.230. Inspect show ip route.
Expected Behavior: Cisco IOS will not install the static route into the forwarding table because the next-hop address cannot be resolved via ARP on any connected subnet.