Changes between Version 47 and Version 48 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute


Ignore:
Timestamp:
03/02/17 10:08:39 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute

    v47 v48  
    151151Many times it is useful to see the OpenFlow messages being exchanged between your controller and the switch. This will tell you whether the messages that are created by your controller are correct and will allow you to see the details of any errors you might be seeing from the switch. You can use Wireshark on both ends of the connection; in hardware switches you have to rely only on the controller view.
    152152
    153 The controller host and OVS has the Wireshark application already installed, including the openflow dissector. For more information on Wireshark you can take a look at the [http://wiki.wireshark.org/ Wireshark wiki].
     153The controller host and OVS has the Wireshark application already installed, including the !OpenFlow dissector. For more information on Wireshark you can take a look at the [http://wiki.wireshark.org/ Wireshark wiki].
    154154
    155155[[Image(GENIExperimenter/Tutorials/Graphics:4NotesIcon_512x512.png, 5%, nolink)]]
    156156To display the Wireshark window on your local host you must ''' ''setup X11 forwarding'' ''', many sites are available that explain how this is done. This is [http://www.seas.upenn.edu/cets/answers/x11-forwarding.html an example] that provides instructions for Windows, Linux and MAC operating systems.
    157157
    158 Here is how to use the OpenFlow dissector for Wireshark on the reserved controller host.
     158Here is how to use the !OpenFlow dissector for Wireshark on the reserved controller host.
    159159
    160160If you are on a Linux friendly machine (this includes MACs) open a terminal and ssh to your controller machine using the -Y command line argument, i.e.
    … …  
    191191}}}
    192192
    193 In the output, we obtain a list of the OpenFlow device (i.e OVS) that Floodlight Controller has learned about.
     193In the output, we obtain a list of the !OpenFlow device (i.e OVS) that Floodlight Controller has learned about.
    194194
    195195Next, ''ping'' Host2 & Host3 from Host1 and then re-run the command. Note that you output details will differ.
    … …  
    248248=== 4g. Run a Port Forwarding Controller ===
    249249
    250 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.
     250Now 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.
    251251
    252252