Router 4

On Router 4, issue a ping command to the so-0/0/0 interface of Router 1 to send traffic across the IPSec tunnel.

user@R4> ping 10.1.12.2

PING 10.1.12.2 (10.1.12.2): 56 data bytes

64 bytes from 10.1.12.2: icmp_seq=0 ttl=253 time=0.937 ms

64 bytes from 10.1.12.2: icmp_seq=1 ttl=253 time=0.872 ms

^C

--- 10.1.12.2 ping statistics ---

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max/stddev = 0.872/0.905/0.937/0.032 ms

You can also issue the traceroute command to verify that traffic to 10.1.12.2 travels over the IPSec tunnel between Router 3 and Router 2. Notice that the second hop does not reference 10.1.15.1—the physical interface on Router 2. Instead, the loopback address of 10.0.0.2 on Router 2 appears as the second hop. This indicates that the IPSec tunnel is operating correctly.

user@R4> traceroute 10.1.12.2

traceroute to 10.1.12.2 (10.1.12.2), 30 hops max, 40 byte packets

 1  10.1.56.1 (10.1.56.1)  0.670 ms  0.589 ms  0.548 ms

 2  10.0.0.2 (10.0.0.2)  0.815 ms  0.791 ms  0.763 ms

 3  10.1.12.2 (10.1.12.2)  0.798 ms  0.741 ms  0.714 ms