06-04-2013 10:40 AM - edited 03-04-2019 08:06 PM
Hello,
I built the attached topology with Packet Tracer. In the Miami LAN I can ping all other hosts including the default gateway and therfore all interfaces
on the Miami router, however I cannot ping the Nashville router. For some reason, traffic will not travel passed that point. I have the same issue
with the Nashville LAN. I cannot get traffic to go beyond the LAN. I did enable RIP version 2 on all routers, but there does not seem to be any chatting going on between the routers either? There is no entry in the routing tables for the remote networks.. ?
Any help would be MUCH appreciated.
Thanks!
Solved! Go to Solution.
06-04-2013 11:14 AM
Hi you need to advertise the LAN & WAN subnet then only you can communicate between 2 locations.
So you need to add the below command on all routers (Miami, Nashville, San Francisco).
!
router rip
version 2
network 172.16.0.0
no auto-summary
!
Need to add the below command on Ft Worth router.
!
router rip
version 2
network 172.16.0.0
network 200.100.100.0
no auto-summary
!
You can verify by using this command sh ip protocol it will show interface which is participating in RIP routing protocol.
Router1#sh ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 4 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Serial0/0/0 2 2
Serial0/1/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.16.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
172.16.1.6 120 00:00:24
172.16.1.1 120 00:00:16
Distance: (default is 120)
SERVER>ipconfig
FastEthernet0 Connection:(default port)
Link-local IPv6 Address.........: ::
IP Address......................: 172.16.2.18
Subnet Mask.....................: 255.255.255.240
Default Gateway.................: 172.16.2.17
SERVER>
SERVER>ping 172.16.2.4
Pinging 172.16.2.4 with 32 bytes of data:
Request timed out.
Reply from 172.16.2.4: bytes=32 time=47ms TTL=126
Reply from 172.16.2.4: bytes=32 time=31ms TTL=126
Reply from 172.16.2.4: bytes=32 time=47ms TTL=126
Ping statistics for 172.16.2.4:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 47ms, Average = 41ms
SERVER>
06-04-2013 11:14 AM
Hi you need to advertise the LAN & WAN subnet then only you can communicate between 2 locations.
So you need to add the below command on all routers (Miami, Nashville, San Francisco).
!
router rip
version 2
network 172.16.0.0
no auto-summary
!
Need to add the below command on Ft Worth router.
!
router rip
version 2
network 172.16.0.0
network 200.100.100.0
no auto-summary
!
You can verify by using this command sh ip protocol it will show interface which is participating in RIP routing protocol.
Router1#sh ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 4 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Serial0/0/0 2 2
Serial0/1/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.16.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
172.16.1.6 120 00:00:24
172.16.1.1 120 00:00:16
Distance: (default is 120)
SERVER>ipconfig
FastEthernet0 Connection:(default port)
Link-local IPv6 Address.........: ::
IP Address......................: 172.16.2.18
Subnet Mask.....................: 255.255.255.240
Default Gateway.................: 172.16.2.17
SERVER>
SERVER>ping 172.16.2.4
Pinging 172.16.2.4 with 32 bytes of data:
Request timed out.
Reply from 172.16.2.4: bytes=32 time=47ms TTL=126
Reply from 172.16.2.4: bytes=32 time=31ms TTL=126
Reply from 172.16.2.4: bytes=32 time=47ms TTL=126
Ping statistics for 172.16.2.4:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 47ms, Average = 41ms
SERVER>
06-05-2013 06:24 AM
Awwww light bulb
Thanks.
05-27-2015 11:35 PM
help me to do the same topology with step by step commands
05-29-2015 02:28 PM
feel free to download the attachment. It's a .pkt file and should open in packet tracer. You can use that config or build your own mirroring it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide