Commit d756a294 authored by Leigh B. Stoller's avatar Leigh B. Stoller

Add Static routing to IP routing section.

parent cd2094d5
...@@ -707,25 +707,23 @@ provided FreeBSD or Linux disk images. ...@@ -707,25 +707,23 @@ provided FreeBSD or Linux disk images.
<p> <p>
You can use the NS <tt>rtproto</tt> syntax in your NS file to enable You can use the NS <tt>rtproto</tt> syntax in your NS file to enable
automatic routing: routing:
<code><pre> <code><pre>
$ns rtproto <i>protocol</i> $ns rtproto <i>protocol</i>
</pre></code> </pre></code>
where the <i>protocol</i> option for automated routing is currently where the <i>protocol</i> option is limited to one of
limited to <code>Session</code>. The current implementation of <code>Session</code>, <code>Static</code>, or <code>Manual</code>.
<code>Session</code> routing is to enable <code>gated</code> running <code>Session</code> routing provides fully automated routing support,
the OSPF protocol on all nodes in the experiment. and is implemented by enabling <code>gated</code> running the OSPF protocol
In the future we may add support for other routing protocols as well on all nodes in the experiment. <code>Static</code> routing also
as the ability to have Emulab automatic pre-compute static routes based provides automatic routing support, but rather than computing the
on an experiment's topology. routes dynamically, the routes are precomputed when the experiment is
created, and then loaded on each node when it boots.
<p>
We also support a facility allowing you to explicitly specify per-node <p>
routing information in the NS file. To do this, <code>Manual</code> routing allows you to explicitly specify per-node
use the <tt>Manual</tt> routing option to <tt>rtproto<tt>: routing information in the NS file. To do this, use the
<code><pre> <tt>Manual</tt> routing option to <tt>rtproto<tt>,
$ns rtproto Manual
</pre></code>
followed by a list of routes using the <tt>add-route</tt> command: followed by a list of routes using the <tt>add-route</tt> command:
<code><pre> <code><pre>
$node add-route $dst $nexthop $node add-route $dst $nexthop
...@@ -737,7 +735,6 @@ $client add-route $server $router ...@@ -737,7 +735,6 @@ $client add-route $server $router
$client add-route [$ns link $server $router] $router $client add-route [$ns link $server $router] $router
$client add-route $serverlan $router $client add-route $serverlan $router
</pre></code> </pre></code>
Note that you would need a separate <code>add-route</code> command to Note that you would need a separate <code>add-route</code> command to
establish a route for the reverse direction; thus allowing you to establish a route for the reverse direction; thus allowing you to
specify differing forward and reverse routes if so desired. specify differing forward and reverse routes if so desired.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment