Conti vity 251 ABOT D eployment Version 1.0 April 26, 20043.7.8 Test VPN Client TunnelFor a success VPN Client tunnel connection:• PC S4 (behind C251)should be able to ping PC S3 (behind C1100)• PC S3 should be able to ping the address (172.16.55.10) assigned to C251, but notfurther to the LAN behind C1100.• PC S3 should be able to remotely manage C251 with FTP, Telnet, HTTP using theassigned IP address of 172.16.55.10.Ping from PC S4 to PC S3C:\>ping -t 192.168.3.9Pinging 192.168.3.9 with 32 bytes of data:Reply from 192.168.3.9: bytes=32 time=31ms TTL=126Reply from 192.168.3.9: bytes=32 time=29ms TTL=126Reply from 192.168.3.9: bytes=32 time=29ms TTL=126Reply from 192.168.3.9: bytes=32 time=30ms TTL=126Reply from 192.168.3.9: bytes=32 time=30ms TTL=126Reply from 192.168.3.9: bytes=32 time=32ms TTL=126Reply from 192.168.3.9: bytes=32 time=29ms TTL=126Reply from 192.168.3.9: bytes=32 time=29ms TTL=126Reply from 192.168.3.9: bytes=32 time=28ms TTL=126Reply from 192.168.3.9: bytes=32 time=29ms TTL=126Reply from 192.168.3.9: bytes=32 time=28ms TTL=126Ping statistics for 192.168.3.9:Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 28ms, Maximum = 32ms, Average = 29msControl-C^CC:\>Ping from PC S3 to 171.16.55.10 (C251 assigned address)C:\Documents and Settings\Administrator>ping 172.16.55.10Pinging 172.16.55.10 with 32 bytes of data:Reply from 172.16.55.10: bytes=32 time=30ms TTL=253Reply from 172.16.55.10: bytes=32 time=20ms TTL=253Reply from 172.16.55.10: bytes=32 time=30ms TTL=253Reply from 172.16.55.10: bytes=32 time=20ms TTL=253