Changes between Version 17 and Version 18 of WARPLab/QuickStart

Timestamp:

Mar 29, 2013, 9:54:25 AM (11 years ago)

Author:

chunter

Comment:

--

WARPLab/QuickStart

@@ -60 +60 @@
 }}}
 
-As a more concrete example, the quick start step above that called the command {{{wl_nodeCmd(nodes,'identify');}}}. An equivalent way of issuing this command to the nodes in the network is {{{nodes.wl_nodeCmd('identify');}}}
+As a more concrete example, consider the quick start step above that called the command {{{wl_nodeCmd(nodes,'identify');}}}. An equivalent way of issuing this command to the nodes in the network is {{{nodes.wl_nodeCmd('identify');}}}
 
 
 === Jumbo Frames ===
+The WARP hardware design supports Ethernet packets up to 9000 bytes. Any Ethernet packet larger than 1500 bytes is considered a "jumbo frame" and support for these jumbo frames among consumer NICs and switches is limited.
+
+==== Ping Test ====
+
+==== WARPLab Test ====
+
+==== Known Compatible Hardware ====
+
+==== Known Partially Compatible Hardware ====
+
+==== Known Incompatible Hardware ====
+
 === pnet Toolbox ===
 By default, WARPLab will use built-in java routines for performing network I/O. pnet, a custom UDP mex toolbox for matlab, is also supported, but the latest version is required. pnet can offer modestly higher performance than the built-in java routines, but the usage of WARPLab is otherwise identical. If you want to use pnet, please perform the following steps: