Changes between Version 9 and Version 10 of Tutorials/c0WiFi/Tutorial3
- Timestamp:
- May 25, 2016, 1:45:39 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/c0WiFi/Tutorial3
v9 v10 7 7 === Experiment Script === 8 8 9 The experiment script is shown below. Near the top of the script we define an application header for iperf. After which we define two groups - the first group (AP) consists of a single node to be configured as an access point. The second group (client) can be a single or multiple node(s) that will be configured as WiFi clients. Both groups add the iperf application and configure the wireless interfaces accordingly. At the bottom of the script, the nodes in all the defined groups are brought up and the applications are executed.9 The experiment script is shown below. Near the top of the script we define an application header for iperf. After which we define two groups - the first group (AP) consists of a single node to be configured as an access point. The second group (client) can be a single or multiple node(s) that will be configured as !WiFi clients. Both groups add the iperf application and configure the wireless interfaces accordingly. At the bottom of the script, the nodes in all the defined groups are brought up and the applications are executed. 10 10 11 11 {{{ … … 258 258 3. The wireless card properties are set using with the ''node.net.w0'' parameters. Note that we set ''node.net.w0.mode'' to ''managed'' to configure the wireless card as client. Other relevant parameters are also set here as well. Since we can have multiple nodes in a group we specify ''node.net.w0.ip'' with the last byte of the IP address as %index%. In this way each node will have a unique address. 259 259 260 * At the end of the script once all the nodes are at the same point and all applications have been initialized, an event is triggered to continue and execute the remaining steps. The 10 second delay before the call to ''startApplications'', this allows time for the clients to establish a wifi connection with the access point before continuing. Iperf is started on all the nodes, execution of experiment script is delayed again giving time to collect experiment data. Finally all applications are stopped and the experiment exits out.260 * At the end of the script once all the nodes are at the same point and all applications have been initialized, an event is triggered to continue and execute the remaining steps. The 10 second delay before the call to ''startApplications'', this allows time for the clients to establish a !WiFi connection with the access point before continuing. Iperf is started on all the nodes, execution of experiment script is delayed again giving time to collect experiment data. Finally all applications are stopped and the experiment exits out. 261 261 {{{ 262 262 onEvent(:ALL_UP_AND_INSTALLED) do |event| … … 275 275 An overview on running experiment scripts on the orbit testbed can be found on the [wiki:Documentation/CGettingStarted Getting Started Page]. 276 276 277 In order to run this experiment script, load the ''baseline.ndz'' image onto nodes with WiFi cards. Check the ''Status Page' in the [https://www.orbit-lab.org/cPanel/controlPanel/start Control Panel] to find nodes with aWiFi card.277 In order to run this experiment script, load the ''baseline.ndz'' image onto nodes with !WiFi cards. Check the ''Status Page' in the [https://www.orbit-lab.org/cPanel/controlPanel/start Control Panel] to find nodes with a !WiFi card. 278 278 {{{ 279 279 user@console:~$ omf load -i baseline.ndz -t node1-1,node1-2