Changes between Version 1 and Version 2 of GENIExperimenter/Tutorials/GREESC13/OpenFlowWiMAX/Execute

Timestamp:

06/24/13 15:19:20 (11 years ago)

Author:

Ryan Izard

Comment:

--

GENIExperimenter/Tutorials/GREESC13/OpenFlowWiMAX/Execute

@@ -41 +41 @@
    $ cd eth_control
    $ ./delete_route.sh
-   Verify the new routing table has a default route via the br_tap interface no routes via the br_wimax and br_wifi 
-
-interfaces.
+   }}}
+   Verify the new routing table has a default route via the br_tap interface no routes via the br_wimax and br_wifi interfaces.
    3.  In Eclipse, run Floodlight by browsing to '''Run-->Run'''. Note the console output shown toward the bottom of the 
-
 Eclipse window. Since OVS is running, and the '''system_setup.sh''' script pointed each OVS bridge to the Floodlight 
-
 controller, you should see where each switch DPID connects to Floodlight.
    4.  In the Root Terminal, open an new tab (File-->Open Tab) or switch to an unused tab. Browse to the '''/root/06-03-
-
 13/eth_control''' directory.
    5.  In this directory are some Python scripts to manually add and remove flows in the OVS bridges. These scripts 
-
 leverage the Static Flow Pusher REST API present in the Floodlight controller. Since we have previously disabled 
-
 Forwarding, flows added by the Static Flow Pusher will be the only flows present on the switches, and thus only traffic 
-
 permitted by these flows will traverse the OVS network. These flows essentially take packets from a particular ingress 
-
 port and send them out a destination port. To do this, we need to determine the port numbers Floodlight has associated 
-
 with the ports of our OVS bridges. The Floodlight REST API is a means of obtaining data from the Floodlight controller. We 
-
 need to send a query to Floodlight asking for what it knows about any connected switches.
    {{{
@@ -275 +265 @@
    }}}
    Above is sample output from the query issued. The output is organized by switch -- there should be three -- br_tap, 
-
 br_wifi, and br_wimax. On each of these switches, you can see the ports and the names of the ports as they were given in 
-
 '''system_setup.sh'''. Take note of the port numbers for the patch ports on each switch, as well as the port numbers for 
-
 the interface port on each switch.
    6.  Armed with this information, we can now create the flows we want to insert on each switch. Namely, we can specify 
-
 and ingress and output port on br_tap, br_wifi, and br_wimax for packets traveling in each direction. In the Root 
-
 Terminal, open the Python script '''gree13_switchWiFi.py''' with your favorite text editor. This script is designed to 
-
 switch to the WiFi interface.
    {{{
    $ gedit gree13_switchWiFi.py
-
 import httplib
 import json
-
 class StaticFlowPusher(object):
-
     def __init__(self, server):
         self.server = server
@@ -418 +399 @@
    }}}
    In this script, there are four flows for each OVS bridge -- two for outgoing packets and two for incoming packets. Why 
-
 two? OpenFlow filters packets by not only data like MAC and IP addresses, but also by the type of packet (its 
-
 '''ethertype'''). We need to forward all IP (ethertype=0x800) and all ARP (ethertype=0x806) packets in each direction in