Changes between Version 5 and Version 6 of Internal/OpenFlow/OFIntro

Timestamp:

Jul 26, 2013, 12:37:31 AM (11 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/OFIntro

@@ -18 +18 @@
  * [http://docs.projectfloodlight.org/display/floodlightcontroller/Cbench+(New) cbench] : Controller benchmarking tool 
  * [http://www.openflow.org/wk/index.php/Liboftrace liboftrace] : !OpenFlow message parser/analyzer for pcap files   
+ * [https://bitbucket.org/barnstorm/of-dissector Wireshark+OF dissector] : Wireshark with a dissector for !OpenFlow messages
 
 This makes things easy since you can image multiple nodes with the same image, and pick and choose what to run where. 
@@ -115 +116 @@
  }}}
 
+=== 1.2.1 Using Wireshark ===
+In the above example, `tcpdump` can be replaced by `wireshark`. Wireshark is "friendlier" in that it has a GUI and an !OpenFlow dissector plugin is available for it. In order to use Wireshark, you must enable X11 forwarding from your workstation to the node, with the -X or -Y flag for `ssh` e.g.:
+{{{
+ssh -X -l root node1-1
+}}} 
+
 == Using OpenVswitch directly ==
 Mininet's datapaths are backed by OVS. Therefore, if you have a Mininet install, you get OVS for "free". You can use OVS directly for your data plane. 
 
-= Multiple controller instances = 
+= II More complex examples = 
 You can launch multiple instances of Floodlight on one or more nodes. If you decide to run the instances on a single host, the ports used by the Floodlight instances must not conflict i.e. each instance must be assigned a different set of ports. 
   
 ----
-= Installation = #install
+= III Installation = #install
 The following are the installation steps and basic usage for the software that are found on the image. For more information, refer to their respective pages; Floodlight and Mininet in particular have very thorough docs. 
 
 Quick links: [[BR]]
- [#floodlight 2.1 Floodlight][[BR]]
- [#mn 2.2 Mininet][[BR]]
- [#cbench 2.3 CBench] [[BR]]
- [#loft 2.4 liboftrace] [[BR]]
-
+ [#floodlight 3.1 Floodlight][[BR]]
+ [#mn 3.2 Mininet][[BR]]
+ [#cbench 3.3 CBench] [[BR]]
+ [#loft 3.4 liboftrace] [[BR]]
+ [#ws 3.5 Wireshark] [[BR]]
+
+Note, the following examples are for Ubuntu, since that's what is used at WINLAB. A quick search will often bring up hints/steps for CentOS/RHEL and OSX, but for the most part, you will have to experiment a bit. 
+ 
 == 2.1 Floodlight == #floodlight
 docs: http://docs.projectfloodlight.org/display/floodlightcontroller/Floodlight+Documentation [[BR]]
@@ -436 +446 @@
 # ofstats sample.pcap 192.168.1.5 6637 > outfile
 }}} 
+
+== 3.5 Wireshark == #ws
+website(wireshark): http://www.wireshark.org [[BR]]
+docs(plugin): https://bitbucket.org/barnstorm/of-dissector
+
+=== dependencies ===
+wireshark(source):
+{{{
+sudo apt-get install libpcap-dev bison flex libgtk2.0-dev build-essential 
+}}}
+plugin:
+{{{
+sudo apt-get install scons mercurial
+}}}
+
+=== installation/build ===
+You need the source for Wireshark to build the plugin. At the time of this writing Wireshark is at v.1.10.  
+{{{
+wget http://wiresharkdownloads.riverbed.com/wireshark/src/wireshark-1.10.0.tar.bz2
+tar -xjf wireshark-1.10.0.tar.bz2 
+cd wireshark-1.10.0/
+./configure
+}}}
+
+The above is sufficient for the plugin. Installing Wireshark from source e.g. with `make;make install` can take a while, so you may choose to install the binary, i.e. do:
+{{{
+apt-get install wireshark
+}}}
+If you decide to build from source, also install `libwiretap1`.
+
+Next fetch and build the plugin:
+{{{
+hg clone https://bitbucket.org/barnstorm/of-dissector
+cd of-dissector/
+export WIRESHARK=${WS_ROOT}/wireshark-1.10.0/
+cd src
+scons install
+cp openflow.so /usr/local/lib/wireshark/plugins/1.10.0/
+}}}
+Where ${WS_ROOT} is the directory you've untarred the Wireshark source to. 
+
+=== run ===
+Run Wireshark as root:
+{{{
+sudo wireshark
+}}}
+
+You should see openflow.so in the list of plugins if you go to Help > About Wireshark > plugins.