Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Is this even possible?

Status
Not open for further replies.

hexn

ISP
Oct 19, 2001
282
US
How is it possible to setup a static route to a router that is 2 hops away? I am routing a subnet to 10.0.0.1, but that IP address belongs to a router that is 2 hops away. How is that possible? 10.0.0.1 is reachable, but I just dont understand how you can route traffic to that interface when you have to jump multiple routers to get there.

I am going insane trying to figure it out!!! Shnypr.com
Idontthinkmyspacebarisworking.....
 
What routing protocol are you running. When you type
sh ip route is the ip address of the 2nd hop showing connected to the interface? I think and heck I could be off base, however I believe that if your running a protocol that sees the ip than the static route will follow the path. I'm sure Wybnormal could answer this in greater detail. Jeter@LasVegas.com
J.Fisher CCNA
 
Thanks Jeter, it all makes sense now. ~~~~~~~~~~
shnypr-small.gif

tech@shnypr.com
~~~~~~~~~~
 
All you do when you create static routes is tell your router what the next hop is to get to the destination network. You're pointing it in the right direction!

So, if you have three routers, A, B, and C and you want to get to the ethernet network on router C from the ethernet network on router A, you could use static routes! Router B would know about the directly connected ports on routers A and C, but wouldn't know about the networks on the other interfaces of routers A and C. For this you could create static routes on router B to say:

To get to the eth network on router A, go via the serial port on router A at this address. Router A will then be able to route the packets from it's serial interface to the eth interface.

The same would go for router C!

So, now router B knows about it's directly connected interfaces on routers A and C, and also about the other networks on routers A and C.

Now, you can tell router A how to get to router C. You point the traffic at router B which knows about the networks on router C.

You can also tell router C how to get to router A. Point traffic at router B, which knows how to get to all the networks on router A.

Now all three routers know how to get to all the available networks! Easy!!

Of course, as the number of routers grows and alternate paths become available, it would be better to implement dydmanic routing, using IGRP or EIGRP, but that's another story!!

Take care!

Chris.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top