Changes between Version 58 and Version 59 of GEC16Agenda/OpenFlow/Instructions/Execute

Timestamp:

03/21/13 06:23:43 (11 years ago)

Author:

nriga@bbn.com

Comment:

--

GEC16Agenda/OpenFlow/Instructions/Execute

@@ -188 +188 @@
 Can you tell now why there were packets flowing even after you killed your controller?
 
-== Run a traffic duplication controller ==
-In the above example we ran a very simple controller. The power of OpenFlow comes from the fact that you can decide to forward the packet anyway you want based on the supported OpenFlow actions. A very simple but powerful modification you can do, is to duplicate all the traffic of the switch out a specific port. This is very useful for application and network analysis. You can imagine that at the port where you duplicate traffic you connect a device that does analysis. Our hosts are VMs so we are going
-to verify the duplication by doing a `tcpdump`  on the port on the ovs switch. 
-
-  1. Open a new terminal to the OVS switch. 
-
-  2. Look at the sliver details page in the portal and see what interface is bound to OVS:if2 and run tcpdump on the interface. This will allow you to see all traffic going out that interface
-  {{{
-  sudo tcpdump -i ethX
-  }}}
-
-  2. In the other ovs host go under the `/local/pox/ext` directory:
-  {{{
-   cd ext
-  }}}
-
-  2. There you would see two files :
-     i. myDuplicateTraffic.py : this is the file that has instructions about how to complete the missing information, go ahead and try to implement your first controller. 
-     ii. !DuplicateTraffic.py : this has the actual solution you can just run this if you don't want to bother with writing a controller. 
-
-   To run the controller do (while at /local/pox directory)
-    {{{
-    ./pox.py --verbose myDuplicateTraffic --duplicate_port=ethX
-    }}}
-   
-    To test it go to the terminal of host1 and try to ping host2:
-    {{{
-    ping 10.10.1.2
-    }}}
-
-    At the terminal of host2, do a tcpdump on the dataplane interface (the one that starts with 'mv', use /sbin/ifconfig to get a list):
-    {{{
-    sudo tcpdump -i ethY
-    }}}
-
-    If your controller is working you the packets registering in both terminals that you run tcpdump. 
-
 == Useful Tips for writing your controller ==
 In order to make this first experience of writing controller easier, we wrote some helpful functions that will abstract some of the  particularities of PoX away. 
@@ -247 +210 @@
   * createArpReply : Create an Arp Reply for  a different source IP
 
+== Run a traffic duplication controller ==
+In the above example we ran a very simple controller. The power of OpenFlow comes from the fact that you can decide to forward the packet anyway you want based on the supported OpenFlow actions. A very simple but powerful modification you can do, is to duplicate all the traffic of the switch out a specific port. This is very useful for application and network analysis. You can imagine that at the port where you duplicate traffic you connect a device that does analysis. Our hosts are VMs so we are going
+to verify the duplication by doing a `tcpdump`  on the port on the ovs switch. 
+
+  1. Open a new terminal to the OVS switch. 
+
+  2. Look at the sliver details page in the portal and see what interface is bound to OVS:if2 and run tcpdump on the interface. This will allow you to see all traffic going out that interface
+  {{{
+  sudo tcpdump -i ethX
+  }}}
+
+  2. In the other ovs host go under the `/local/pox/ext` directory:
+  {{{
+   cd ext
+  }}}
+
+  2. There you would see two files :
+     i. myDuplicateTraffic.py : this is the file that has instructions about how to complete the missing information, go ahead and try to implement your first controller. 
+     ii. !DuplicateTraffic.py : this has the actual solution you can just run this if you don't want to bother with writing a controller. 
+
+   To run the controller do (while at /local/pox directory)
+    {{{
+    ./pox.py --verbose myDuplicateTraffic --duplicate_port=ethX
+    }}}
+   
+    To test it go to the terminal of host1 and try to ping host2:
+    {{{
+    ping 10.10.1.2
+    }}}
+
+    At the terminal of host2, do a tcpdump on the dataplane interface (the one that starts with 'mv', use /sbin/ifconfig to get a list):
+    {{{
+    sudo tcpdump -i ethY
+    }}}
+
+    If your controller is working you the packets registering in both terminals that you run tcpdump. 
 
 == Run a port forward Controller ==