|
Home > Archive > 70-218 > March 2003 > "route add" question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
"route add" question
|
|
|
|
|
| Hi ruscorp,
Yes, "B" is the correct answer, and I'll take a stab at an explanation for you. As Freak once told me when I was trying to understand a route print command display, "Be the packet".
Basically the command breaks down to Route Add <destination network> mask gateway -p (persistent route).
NYROUTE1 is currently only aware of the 10.1.2.0, 10.1.3.0 and 10.1.4.0 subnetworks. It can successfully route packets to any of these 3 subnetworks. However, it is not aware of the 10.1.5.0 network or where to send packets that are destined for the 10.1.5.0 network.
So establshing a persistent route via the Route Add command on the NYROUTE1 box is telling the NYROUTE1 box that any packet destined for the 10.1.5.0 network should be sent to the 10.1.4.253 gateway, which is the interface on the BOSROUTE1 box which knows about the 10.1.5.0 network and will handle directing the packet to BOSFP01 at 10.1.5.5.
If we do not establish this route on NYROUTE1, anything destined for the 10.1.5.0 network will get dropped at this point because the NYROUTE1 box does not know where to send the 10.1.5.0 subnetwork destined packet regardless as to whether the client is in London or New York for that matter.
Hope this helps! | |
| ruscorp 2002-09-05, 10:09 am |
| Spid: Thanks for the info!  | |
| wertop 2003-03-08, 9:44 am |
| Yes, the answer in EasyCert is correct.
Thanks for the info Spid! |
|
|
|
|