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


Ignore:
Timestamp:
10/19/12 02:49:35 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC15Agenda/AdvancedGENITopoOmni/Instructions/ClickExampleExperiment

    v6 v7  
    262262== 5. Start your routers ==
    263263
    264 The extractor script produces a click configuration file for each of your routers.  ''On each of your four router hosts,'' run this command:
    265 
    266 {{{
    267 sh ./startClick.sh
    268 }}}
    269 
    270 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.
    271 
    272 {{{
     264The extractor script produces a click configuration file for each of your routers. 
     265  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:
     266  {{{
     267  ssh -A <router_nickname> "sh ./startClick.sh"
     268}}}
     269  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.
     270
     271  {{{
    273272Stopping any running Click routers
    274273Starting Click router
     
    281280Congratulations! 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.
    282281
    283 == Send some traffic ==
     282== 6. Send some traffic ==
    284283
    285284Now 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.
    286 
    287 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).
    288 {{{
     285  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).
     286  {{{
    289287[mberman@hostb ~]$ nc -ul 24565
    290288}}}
    291 
    292 Then connect to it from your terminal window on '''hostA''':
    293 {{{
     289  i. Connect to it from your terminal window on '''hostA''':
     290  {{{
    294291[mberman@hosta ~]$ nc -u hostb 24565
    295292}}}