Changes between Version 11 and Version 12 of Tutorials/m0SDN/aHowTo

Timestamp:

Aug 20, 2009, 3:59:37 PM (15 years ago)

Author:

akoshibe

Comment:

—

Tutorials/m0SDN/aHowTo

@@ -102 +102 @@
 ./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:
-
-
-   
+In the !OpenFlow reference system, a log of the verbose output can be saved by appending `--log-file [filename]`.    
 
 === the Wireshark plugin ===
@@ -126 +123 @@
 and on the client:
 {{{
-iperf -c <server ip address>
+iperf -c 192.168.x.y 
 }}}
-
-iperf, however, cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng.
+192.168.x.y is the IP address block associated with the !OpenFlow VLAN. When setting the node IP addresses (i.e. using ifconfig), x.y should be made unique to each node. A caveat is that iperf cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng.
 
 === BWM-ng ===