From: Grant T. <gr...@te...> - 2003-06-11 12:32:35
|
On Tue, Jun 10, 2003 at 11:00:37AM +0900, lance wrote: > Was just doing the static route interactive challenge in 12.5.1 from the > cisco online material. > Any one know why we sett a static route between router Lab_A and Lab_D > when they are not > Directly connected. I thought that was the point of a static route. It > appears that Lab_B is the forwarding > Router but there is no mention of lab_C which is on the route to Lab_D > after Lab_B. > > What am I missing here? Actually, I think you've got it backwards. You only need a static route for a network that's not directly connected. A router already knows how to get to a directly connected network, just put it out the interface with the IP address in that network. You need a static route to tell it how to get to a non-directly connected network. A static route is not the whole path to the destination network, it's just the next hop. So to get from A to D, you have to go through B and C. But all the router needs to know is the next hop, that is, Lab_B. It's up to Lab_B to know how to get to D (through C). In a dumb network, B wouldn't know how to get to D without another static route to D through C. However, this is where routing protocols come in, to automate all this. > It seems funny to set a static route without specifying the whole > path. Only because it's still new. :) -- Grant Tester +61 413 987 988 |