Changes between Version 2 and Version 3 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
- Timestamp:
- 10/30/16 21:59:34 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
v2 v3 20 20 Now that the switch is up and running we are ready to start working on the controller. For this tutorial we are going to use the [https://floodlight.atlassian.net/wiki/spaces/floodlightcontroller Floodlight Controller]. We installed the software for running Floodlight in the controller host in [wiki:GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup#con Configure the Floodlight Controller] section. 21 21 22 === 3a. Login to your hosts ===22 === 4a. Login to your hosts === 23 23 24 24 To start our experiment we need to ssh all of our hosts. … … 33 33 Depending on which tool and OS you are using there is a slightly different process for logging in. If you don't know how to SSH to your reserved hosts learn [wiki:HowTo/LoginToNodes how to login.] Once you have logged in follow the rest of the instructions. 34 34 35 === 3b. Use a Learning Switch Controller ===35 === 4b. Use a Learning Switch Controller === 36 36 37 37 In this example we are going to run a very simple learning switch controller to forward traffic between `host1` and `host2`. … … 142 142 }}} 143 143 144 === 3b. Look around your OVS switch ===144 === 4c. Look around your OVS switch === 145 145 146 146 1. If you are using OVS, to see the flow table entries on your OVS switch: … … 182 182 Can you tell now why there were packets flowing even after you killed your controller? 183 183 184 === 3d. Download the pox apps ===184 === 4d. Download the pox apps === 185 185 To help you get started with your controller writing, we will provide: 186 186 * skeleton files for the controllers where you only need to complete some missing functionality … … 217 217 * createArpReply : Create an Arp Reply for a different source IP 218 218 219 === 3e. Debugging your Controller ===219 === 4e. Debugging your Controller === 220 220 While you are developing your controller, some useful debugging tools are: 221 221 … … 254 254 listening on. And once you have lines, you can choose one of the lines and choose "Decode as ...." and choose the ''OFP protocol''. 255 255 256 === 3f. Run a traffic duplication controller ===256 === 4f. Run a traffic duplication controller === 257 257 258 258 In the above example we ran a very simple learning switch controller. [[BR]] … … 304 304 }}} 305 305 306 === 3g. Run a port forward Controller ===306 === 4g. Run a port forward Controller === 307 307 308 308 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. … … 359 359 }}} 360 360 361 === 3h. Run a Server Proxy Controller ===361 === 4h. Run a Server Proxy Controller === 362 362 363 363 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.
