Changes between Version 9 and Version 10 of Tutorials/m0SDN/aHowTo

Timestamp:

Aug 20, 2009, 3:16:19 AM (15 years ago)

Author:

akoshibe

Comment:

—

Tutorials/m0SDN/aHowTo

@@ -100 +100 @@
 and in NOX, it is found under .../noxcore/build/src/
 {{{
-./nox-core -v ptcp:6633 
+./nox-core -v -i ptcp:6633 
 }}} 
+In the !OpenFlow reference system, a log of the verbose output can be saved by appending `--log-file [filename]`. The resulting log can for example, be used to visualize the verbosity of the controller - here, the log was parsed using Ruby, and plotted in MATLAB:
+
+
+   
+
 === the Wireshark plugin ===
-The !OpenFlow Reference system comes with an !OpenFlow wireshark dissector. The requirements are wireshark and glib:
+The !OpenFlow Reference system comes with an !OpenFlow wireshark dissector. glib is required for the plugin to work:
 {{{
 apt-get install wireshark libgtk2.0-dev
@@ -110 +115 @@
 sudo make install
 }}}  
+tcpdump pcap files can also be opened using wireshark - once the plugin has been installed, !OpenFlow packets can be interpreted from these files as well.  
+
 === BWM-ng ===
-For performance testing, you may want to run some bandwidth tests. Real-time bandwidth use can be monitored using BWM-ng. By default, the tool will monitor all interfaces on the Console.  
+For performance testing, you may want to run some bandwidth tests. Real-time bandwidth use can be monitored using BWM-ng. By default, the tool will monitor all interfaces on the Console. To just monitor the !OpenFlow interface, you must specify `eth1.100`. To output this to a csv, use the following command: 
+
+{{{
+bwm-ng -I eth1.100 -o csv -t 1000 -F <file-name>
+}}}  
+
+
 
 === Development ===