Changes between Version 13 and Version 14 of Tutorials/c0WiFi/Tutorial3
- Timestamp:
- May 26, 2016, 1:56:06 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/c0WiFi/Tutorial3
v13 v14 33 33 '''2. Define application that will run on nodes:''' 34 34 35 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L8 Lines 8 - 146]35 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L8 Lines 8 - 81] 36 36 37 37 We use ''defApplication'' to define the application header for iperf. This creates a reference name ''iperf'' that can be used later in the script. … … 53 53 '''3. Define properties for group of nodes that will act as !WiFi APs:''' 54 54 55 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L 150 Lines 150 - 159]55 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L83 Lines 83 - 92] 56 56 57 57 The first group (AP) consists of a single node to be configured as an access point. In practice, these property definitions can be applied to multiple nodes (as we will see in the next section). However, for the purposes of this tutorial we will write this particular set of properties assuming it will apply to a single node. … … 82 82 '''4. Define properties for group of nodes that will act as !WiFi clients:''' 83 83 84 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L 161 Lines 161 - 176]84 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L94 Lines 94 - 105] 85 85 86 86 The second group (client) consists of a single or multiple node(s) that will be configured as !WiFi clients. … … 111 111 '''5. Define event that will occur once all nodes are setup and ready:''' 112 112 113 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L1 78 Lines 178 - 187]113 [http://www.orbit-lab.org/attachment/wiki/Tutorials/c0WiFi/Tutorial3/wifi-ap-iperf.rb#L107 Lines 107 - 116] 114 114 115 115 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.
