Collaboration network testbed: Difference between revisions
| Line 13: | Line 13: | ||
= Tests and Results = |
= Tests and Results = |
||
The tests are grouped according to the type of network used when they were performed: [[Collab_Network_Simple_Mesh_Tests|simple mesh]], a [[Collab_Network_School_Mesh_Tests|mesh with a school server]], or [[ |
The tests are grouped according to the type of network used when they were performed: [[Collab_Network_Simple_Mesh_Tests|simple mesh]], a [[Collab_Network_School_Mesh_Tests|mesh with a school server]], or [[Collab_Network_School_Wifi_Tests|access points with a school server]]. |
||
All packet traces are in wireshark format, and contain beacon and link layer management frames as well as IP packets. They were obtained using <tt>tcpdump -i rtapX -w filename</tt>. |
All packet traces are in wireshark format, and contain beacon and link layer management frames as well as IP packets. They were obtained using <tt>tcpdump -i rtapX -w filename</tt>. |
||
Revision as of 03:49, 25 March 2008
While the OLPC Mesh Testbed is conveniently located in the same space used by OLPC for development and business activities, it suffers from an excess of unrelated wireless traffic. In order to allow repeatable testing of larger numbers of laptops, a larger testbed has been set up at another location in the Boston area, where the 802.11b spectrum is relatively unused.
Test Setup
At this location, we currently have a hundred laptops and a school server, along with a separate packet recording machine. Ten laptops are grouped together on each 1.5 m by 0.7 m table. We hope to grow to at least a hundred and fifty laptops over time.
While we will eventually provide remote automated control of large portions of the testing, we are currently performing tests manually.
The laptop developer keying, upgrading, and application installation is done using USB keys.
Tests and Results
The tests are grouped according to the type of network used when they were performed: simple mesh, a mesh with a school server, or access points with a school server.
All packet traces are in wireshark format, and contain beacon and link layer management frames as well as IP packets. They were obtained using tcpdump -i rtapX -w filename.
More specifically, interfaces are configured to the appropriate channels at boot time via ifcfg_ethX files in /etc/sysconfig/network-scripts/ (eth1 to channel 1, eth2 to channel 11, and eth3 to channel 6). There is a script, setup_snoop, for setting up the interfaces which is run once after boot. Another, do_snoop, is used to start logging. Logging is stopped with sudo killall tcpdump
Simple Mesh
In these tests, the laptops are connected solely to one another, through the wireless mesh.
Startup
Write sharing
Read sharing
Chat
School Server Mesh
In these tests, a School server equipped with one to three Active Antenna provides the interconnection for the laptops. In general, the laptops are registered with the school server and using the school's presence service.
Startup & Registration
Presence
Chat
Write sharing
Read sharing
School Server WiFi
In these tests, the laptops are connected to the School server through normal 802.11b/g access points. In general, the laptops are registered with the school server and using the school's presence service.