Changes between Version 12 and Version 13 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute

Timestamp:

11/14/16 03:29:15 (7 years ago)

Author:

pjayanth@bbn.com

Comment:

--

GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute

@@ -159 +159 @@
 === 4f. Topology Details ===
 
-Before we insert flows into the Open vSwitch, we are going to need all the details regarding the topology such as the DPID of the Open vSwitch, MAC addresses of the hosts, the port numbers on which the Hosts are connected to the Open vSwitch etc. These details can be found out by issuing the command:
+Before we insert flows into the Open vSwitch, we are going to need all the details regarding the topology such as the DPID of the Open vSwitch, MAC addresses of the hosts, the port numbers on which the Hosts are connected to the Open vSwitch etc. These details can be found out by issuing the following command in a new Controller terminal:
 
 {{{
@@ -209 +209 @@
 Now let's do a slightly more complicated controller. OpenFlow gives you the power to overwrite fields of your packets at the switch, for example the TCP source or destination port and do port forwarding. You can have clients trying to contact a server at port 5000, and the OpenFlow switch can redirect your traffic to a service listening on port 6000. 
 
-  1. Under the `/tmp/pox/ext` directory there are two files: '''!PortForwarding.py''' and '''myPortForwarding.py''' that are similar like the previous exercise. Both of these controller are configured by a configuration file at `ext/port_forward.config`. Use myPortForwarding.py to write your own port forwarding controller.
-
-  2. To test your controller we are going to use netcat. Go to the two terminals of host2. In one terminal run:
+  
+  1. To test your controller we are going to use netcat. Open two terminals of host2. In one terminal run:
 {{{
 nc -l 5000
@@ -221 +220 @@
 }}}
 
-  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:
+  2. We will check the normal functionality before the flow for a Port Forwarding Controller is inserted. 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
-
-INFO:core:Going down...
-INFO:openflow.of_01:[36-63-8b-d7-16-4b 1] disconnected
-INFO:core:Down.
-}}}
-
-  7. And start your port forwarding controller (if you have written your controller then use myPortForwarding in the following command):
-{{{
-./pox.py --verbose PortForwarding
-}}}
-
-  8. Repeat the netcat scenario described above. Now, your text should appear on the other terminal of host2 which is listening to port 6000. 
-
-
-  9. Stop your port forwarding controller:
-{{{
-DEBUG:myPortForwarding:Got a packet : [02:aa:a3:e8:6c:db>33:33:ff:e8:6c:db IPV6]
-
-INFO:core:Going down...
-INFO:openflow.of_01:[36-63-8b-d7-16-4b 1] disconnected
-INFO:core:Down.
-}}}
+  3. Type something and you should see it at the the terminal of host2 at port 5000. 
+
+  4. Now, we insert the flow for a Port Forwarding Controller:
+{{{
+curl -X POST -d '{"switch":"<DPID OF OPEN vSWITCH>","name":"flow-2","priority":"32768","in_port":"<PORT OF 10.0.0.1>","active":"true", "eth_type":"0x0800", "ip_proto":"0x06", "eth_src":"<MAC OF 10.0.0.1>", "eth_dst":"<MAC OF 10.0.0.2>", "tcp_dst":"5000", "ipv4_src":"10.0.0.1", "ipv4_dst":"10.0.0.2", "actions":"set_field=eth_dst-><MAC OF 10.0.0.2>,set_field=tcp_dst->6000,set_field=ipv4_dst->10.0.0.2,output=<PORT OF 10.0.0.2>"}' http://localhost:8080/wm/staticflowpusher/json
+}}}
+
+  5. In the previous step, we inserted a flow to forward TCP traffic  from Host 1 destined to Host 2 at port 5000 to port 6000. But Host 1 still thinks it is speaking to Host 2 at port 5000. So we need to insert a flow to handle traffic from Host 2 Port 6000 for a seamless transition.
+{{{
+curl -X POST -d '{"switch":"<DPID OF OPEN vSWITCH>","name":"flow-3","priority":"32768","in_port":"<PORT OF 10.0.0.2>","active":"true", "eth_type":"0x0800", "ip_proto":"0x06", "eth_src":"<MAC OF 10.0.0.2>", "eth_dst":"<MAC OF 10.0.0.1>", "tcp_src":"6000", "ipv4_src":"10.0.0.2", "ipv4_dst":"10.0.0.1", "actions":"set_field=tcp_src->5000,output=<PORT OF 10.0.0.1>"}' http://localhost:8080/wm/staticflowpusher/json
+}}}
+
+  6. Repeat the netcat scenario described above. Now, your text should appear on the other terminal of host2 which is listening to port 6000. 
+
 
 === 4h. Run a Server Proxy Controller ===
@@ -264 +244 @@
 As our last exercise, instead of diverting the traffic to a different server running on the same host, we will divert the traffic to a server running on a different host and on a different port. 
 
-  1. Under the `/tmp/pox/ext/` directory there are two files: '''Proxy.py''' and '''myProxy.py''' that are similar like the previous exercise. Both of these controllers are configured by the configuration file `proxy.config`. Use myProxy.py to write your own proxy controller.
-
-  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. 
+  1.  On the terminal of `host3` run a netcat server:
+{{{
+nc -l 6000
+}}}
+
+  3. On the controller host, we will insert a flow 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. 
      * Is it enough to just change the IP address? 
      * Is it enough to just modify the TCP packets? 
-
-   If you want to see the solution, it's available in file /tmp/pox/ext/Proxy.py file.  
   
-  4. To test your proxy controller run  (if you have written your controller then use myProxy in the following command):: 
-{{{
-cd /tmp/pox
-./pox.py --verbose Proxy
+  4. Insert the following flow in the Controller terminal to implement a Server Proxy Controller: 
+{{{
+curl -X POST -d '{"switch":"<DPID OF OPEN vSWITCH>","name":"flow-4","priority":"32768","in_port":"<PORT OF 10.0.0.1>","active":"true", "eth_type":"0x0800", "ip_proto":"0x06", "eth_src":"<MAC OF 10.0.0.1>", "eth_dst":"<MAC OF 10.0.0.2>", "tcp_dst":"5000", "ipv4_src":"10.0.0.1", "ipv4_dst":"10.0.0.2", "actions":"set_field=eth_dst-><MAC OF 10.0.0.3>,set_field=tcp_dst->6000,set_field=ipv4_dst->10.0.0.3,output=<PORT OF 10.0.0.3>"}' http://localhost:8080/wm/staticflowpusher/json
+}}}
+
+
+  5. In the previous step, we inserted a flow to forward TCP traffic  from Host 1 destined to Host 2 at port 5000 to Host 3 at port 6000. But Host 1 still thinks it is speaking to Host 2 at port 5000. So we need to insert a flow to handle traffic from Host 3 Port 6000 for a seamless transition.
+{{{
+curl -X POST -d '{"switch":"<DPID OF OPEN vSWITCH>","name":"flow-5","priority":"32768","in_port":"<PORT OF 10.0.0.3>","active":"true", "eth_type":"0x0800", "ip_proto":"0x06", "eth_src":"<MAC OF 10.0.0.3>", "eth_dst":"<MAC OF 10.0.0.1>", "tcp_src":"6000", "ipv4_src":"10.0.0.3", "ipv4_dst":"10.0.0.1", "actions":"set_field=eth_src-><MAC OF 10.0.0.2>,set_field=ipv4_src-10.0.0.2>set_field=tcp_src->5000,output=<PORT OF 10.0.0.1>"}' http://localhost:8080/wm/staticflowpusher/json
+
 }}}