Router 1

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

user@R1> ping 10.1.56.2

PING 10.1.56.2 (10.1.56.2): 56 data bytes

64 bytes from 10.1.56.2: icmp_seq=0 ttl=253 time=0.917 ms

64 bytes from 10.1.56.2: icmp_seq=1 ttl=253 time=0.881 ms

64 bytes from 10.1.56.2: icmp_seq=2 ttl=253 time=0.897 ms

64 bytes from 10.1.56.2: icmp_seq=3 ttl=253 time=0.871 ms

64 bytes from 10.1.56.2: icmp_seq=4 ttl=253 time=0.890 ms

64 bytes from 10.1.56.2: icmp_seq=5 ttl=253 time=0.858 ms

64 bytes from 10.1.56.2: icmp_seq=6 ttl=253 time=0.904 ms

^C

--- 10.1.56.2 ping statistics ---

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

round-trip min/avg/max/stddev = 0.858/0.888/0.917/0.019 ms

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

user@R1> traceroute 10.1.56.2

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

 1  10.1.12.1 (10.1.12.1)  0.655 ms  0.549 ms  0.508 ms

 2  10.0.0.3 (10.0.0.3)  0.833 ms  0.786 ms  0.757 ms

3 10.1.56.2 (10.1.56.2) 0.808 ms 0.741 ms 0.716 ms