Changes between Version 125 and Version 126 of GENIExperimenter/Tutorials/OpenFlowOVS/Execute

Timestamp:

03/04/15 14:39:04 (10 years ago)

Author:

rrhain@bbn.com

Comment:

--

GENIExperimenter/Tutorials/OpenFlowOVS/Execute

@@ -237 +237 @@
    
   To see that duplication is happening, on the ovs host, run:  
-  {{{
+{{{
 sudo tcpdump -i <data_interface_name>  [using the data_interface to host2]
 sudo tcpdump -i <data_interface_name>  [using the data_interface to host3]
-  }}}
+}}}
 
 You should see traffic from host1 to host2 showing up in the tcpdump window for host3.  As a comparison, you will notice that no traffic shows up in that window when the controller is running the learning switch.
@@ -249 +249 @@
 
   3. Run your newly written controller on the <data_interface_name> that corresponds to ''OVS:if2'' (which is connected to `host3`):  
-  {{{
+{{{
 cd /tmp/pox
 ./pox.py --verbose myDuplicateTraffic --duplicate_port=<data_interface_name>
-  }}}
+}}}
    
   4. To test it go to the terminal of host1 and try to ping host2:
-  {{{
+{{{
 ping 10.10.1.2
-  }}}
+}}}
   If your controller is working, your packets will register in both terminals running tcpdump. 
 
   5. Stop the POX controller:
-  {{{
+{{{
   DEBUG:myDuplicateTraffic:Got a packet : [02:f1:ae:bb:e3:a8>02:c7:e8:a7:40:65 IP]
   DEBUG:SimpleL2Learning:installing flow for 02:f1:ae:bb:e3:a8.2 -> 02:c7:e8:a7:40:65.[1, 2]
@@ -269 +269 @@
   INFO:core:Down.
   controller:/tmp/pox% 
-  }}}
+}}}
 
 === 3d. Run a port forward Controller ===
@@ -278 +278 @@
 
   2. To test your controller we are going to use netcat. Go to the two terminals of host2. In one terminal run:
-  {{{
+{{{
 nc -l 5000
-  }}}
+}}}
 
   and in the other terminal run
-  {{{
+{{{
 nc -l 6000
-  }}}
+}}}
 
   3. Now, start the simple layer 2 forwarding controller. We are doing this to see what happens with a simple controller.
-  {{{
+{{{
 cd /tmp/pox
 ./pox.py --verbose forwarding.l2_learning
-  }}}
+}}}
 
   4. Go to the terminal of host1 and connect to host2 at port 5000:
-  {{{
+{{{
 nc 10.10.1.2 5000
-  }}}
+}}}
    
   5. Type something and you should see it at the the terminal of host2 at port 5000. 
 
   6. Now, stop the simple layer 2 forwarding controller:
-  {{{
+{{{
   DEBUG:forwarding.l2_learning:installing flow for 02:d4:15:ed:07:4e.3 -> 02:ff:be:1d:19:ea.2
   ^C
@@ -308 +308 @@
   INFO:core:Down.
   controller:/tmp/pox% 
-  }}}
+}}}
 
   7. And start your port forwarding controller:
-  {{{
+{{{
 ./pox.py --verbose myPortForwarding
-  }}}
+}}}
 
   8. Repeat the netcat scenario described above. Now, your text should appear on the other terminal of host2 which is listening to port 6000. 
@@ -319 +319 @@
 
   9. Stop your port forwarding controller:
-  {{{
+{{{
   DEBUG:myPortForwarding:Got a packet : [02:aa:a3:e8:6c:db>33:33:ff:e8:6c:db IPV6]
   ^C
@@ -325 +325 @@
   INFO:openflow.of_01:[36-63-8b-d7-16-4b 1] disconnected
   INFO:core:Down.
-  }}}
+}}}
 
 === 3e. Run a Server Proxy Controller ===
@@ -334 +334 @@
 
   2. On the terminal of `host3` run a netcat server:
-  {{{
+{{{
 nc -l 7000
-  }}}
+}}}
 
   3. On your controller host, open the /tmp/pox/ext/myProxy.py file, and edit it to implement a controller that will divert traffic destined for `host2` to `host3`. Before you start implementing think about what are the side effects of diverting traffic to a different host. 
@@ -345 +345 @@
   
   4. To test your proxy controller run: 
-  {{{
+{{{
 cd /tmp/pox
 ./pox.py --verbose myProxy
-  }}}
+}}}
 
 
   5. Go back to the terminal of `host1` and try to connect netcat to `host2` port 5000
-  {{{
+{{{
 nc 10.10.1.2 5000
-  }}}
+}}}
 
   6. If your controller works correctly, you should see your text showing up on the terminal of `host3`.