Changes between Version 6 and Version 7 of GEC15Agenda/AdvancedGENITopoOmni/Instructions/ClickExampleExperiment

Timestamp:

10/19/12 02:49:35 (12 years ago)

Author:

nriga@bbn.com

Comment:

--

GEC15Agenda/AdvancedGENITopoOmni/Instructions/ClickExampleExperiment

@@ -262 +262 @@
 == 5. Start your routers ==
 
-The extractor script produces a click configuration file for each of your routers.  ''On each of your four router hosts,'' run this command:
-
-{{{
-sh ./startClick.sh
-}}}
-
-You'll get output like this. (Don't worry about the warning messages, Click is just reminding you that you have no IP addresses in your core network.) The shell prompt won't come back, but you'll see the debugging output of the Click router in the terminal window.
-
-{{{
+The extractor script produces a click configuration file for each of your routers.  
+  i. On a local terminal run the following command four time, each time substituting the <router_nickname> with one of the top, bottom, left, right:
+  {{{
+  ssh -A <router_nickname> "sh ./startClick.sh"
+}}}
+  You'll get output like this. (Don't worry about the warning messages, Click is just reminding you that you have no IP addresses in your core network.) The output of the click router is redirected to `/tmp/click.out` on each host. 
+
+  {{{
 Stopping any running Click routers
 Starting Click router
@@ -281 +280 @@
 Congratulations! You are now running a non-IP core network on your four routers, along with a (primitive) non-IP multipath routing algorithm. You're ready to experiment with this configuration.
 
-== Send some traffic ==
+== 6. Send some traffic ==
 
 Now you'll use your two edge hosts, '''hostA''' and '''hostB''' to send traffic along your network.  Since these end hosts are not running your modified protocol, they'll rely on the '''top''' and '''bottom''' routers to transform their IP packets into your modified protocol on entry to the core network and back into IP packets on exit.
-
-In your terminal window on '''hostB''', instruct '''nc''' to listen for a UDP connection on port 24565 (or some other port that catches your fancy).
-{{{
+  i. In your terminal window on '''hostB''', instruct '''nc''' to listen for a UDP connection on port 24565 (or some other port that catches your fancy).
+  {{{
 [mberman@hostb ~]$ nc -ul 24565
 }}}
-
-Then connect to it from your terminal window on '''hostA''':
-{{{
+  i. Connect to it from your terminal window on '''hostA''':
+  {{{
 [mberman@hosta ~]$ nc -u hostb 24565
 }}}