Ccna routing and Switching Complete Study Guide

no ip route 10.1.1.0 255.255.255.0 fa0/0

R2(config)#

ip route 10.1.1.0 255.255.255.0 192.168.10.1

That should do it. Let’s verify from PC1:

C:\Users\Todd Lammle>

ping 172.16.20.254

 

---

Troubleshooting IP Network Connectivity 

841

Pinging 172.16.20.254 with 32 bytes of data:

Reply from 172.16.20.254: bytes=32 time<1ms TTL=128

Reply from 172.16.20.254: bytes=32 time<1ms TTL=128

Reply from 172.16.20.254: bytes=32 time<1ms TTL=128

Reply from 172.16.20.254: bytes=32 time<1ms TTL=128

 

Ping statistics for 172.16.20.254

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Our snag appears to be solved, but just to make sure, we really need to verify with a 

higher-level protocol like Telnet:

C:\Users\Todd Lammle>