Collab Network Simple Mesh Tests

From OLPC

Revision as of 04:26, 16 April 2008 by Wad (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

In these collaboration and networking tests, the laptops are connected solely to one another, through the wireless mesh. Other networking modes tested are simple WiFi, school mesh and school WiFi.

Contents

Startup

Startup is also frequently included in other tests, such as test 0321A and test 0321C.

To reiterate, there is no school mesh present in these tests, or WiFi APs which the laptops have associated with in the past.

Test 0414F

Laptop Build: 703 + libertas firmware 22.p8

This test was a close to simultaneous startup of 28 laptops. 17 out of the 28 had problems joining a simple mesh. Those that joined showed no other laptops. This test was repeated (test 0414G), and the same 17 laptops had the same problem.

Twenty-eight laptops (X50 - X59, X62 - X79) were turned on sequentially, around one laptop every second. Each laptop had previously been registered with a school server.

Seventeen of the laptops did not join a simple mesh (Trac 5848). Failing laptops: X52, X54, X55, X59, X62, X64, X65, X66, X67, X68, X69, X71, X72, X75, X76, X77, X78

Very disturbing was the lack of presence information. No laptop connected to the simple mesh on channel 1 could see any other laptop in their neighborhood view. This is due to changes introduced with the 22.p8 libertas firmware (#6854).

The logging was conducted with three Active Antennas, separated by one meter, all on channel 1.

Packet Traces: Chan 1, Chan 6, Chan 11

Laptop X55 logs: All, /var/log/messages, Telepathy/Sugar

Laptop X64 logs: All, /var/log/messages, Telepathy/Sugar

Laptop X75 logs: All, /var/log/messages, Telepathy/Sugar

Laptop X76 logs: All, /var/log/messages, Telepathy/Sugar

Server logs: /var/log/messages, /var/log/ejabberd, laptop list

Test 0414G

Laptop Build: 703 + libertas firmware 22.p8

This test was a close to simultaneous startup of 28 laptops. 17 out of the 28 had problems joining a simple mesh. The same 17 which had the same problem in test 0414F. Those that joined showed no other laptops.

Twenty-eight laptops (X50 - X59, X62 - X79) were turned on sequentially, around one laptop every second. Each laptop had previously been registered with a school server.

Seventeen of the laptops did not join a simple mesh (Trac 5848). Failing laptops were: X52, X54, X55, X59, X62, X64, X65, X66, X67, X68, X69, X71, X72, X75, X76, X77, X78

The logging was conducted with three Active Antennas, separated by one meter.

Packet Traces: Chan 1, Chan 6, Chan 11

Laptop X72 logs: All, /var/log/messages, Telepathy/Sugar

Laptop X73 logs: All, /var/log/messages, Telepathy/Sugar

Server logs: /var/log/messages, /var/log/ejabberd, laptop list

Test 0414H

Laptop Build: 703 + libertas firmware 22.p8

This test was a close to sequential startup of 5 laptops. 2 out of the 5 had problems joining a simple mesh.

Five laptops (X52, X54, X63, X70, and X74) were turned on sequentially, one laptop every five seconds. Each laptop had previously been registered with a school server.

Two of the laptops (X52 and X54) did not join a simple mesh (Trac 5848).

The logging was conducted with three Active Antennas, separated by one meter.

Packet Traces: Chan 1, Chan 6, Chan 11

Laptop X54 logs: All, /var/log/messages, Telepathy/Sugar

Server logs: /var/log/messages, /var/log/ejabberd, laptop list

Test 0317A

Laptop Build: 699

This was a staged startup of laptops. The packet trace was started five minutes before starting to turn the laptops on. The laptops were turned on in groups of five, with each group allowed to enter simple mesh mode before starting the next group.

The first ten laptops (X50 - X59) came up without a problem, with all laptops able to see the others.

One laptop (X69) in the third group of laptops (X65 - X69) came up without joining a simple mesh (Trac 5848). A reboot fixed the problem.

Another laptop (X73) in the fifth group of laptops (X70 - X74) came up with Trac 5848 and had to be rebooted before joining the simple mesh.

After rebooting two laptops, all 25 laptops (X50 - X74) could see the other 24 in their neighborhood view.

Packet Traces: Chan 1, Chan 11, Chan 6

Discussion of packet traces

Write Sharing

Test 0331A

Laptop Build: 703 + Write 55

This test booted up 28 laptops in a simple mesh. 27 of the 28 successfully joined the simple mesh. A Write activity was then shared with 7 other laptops. 5 of the 7 successfully shared the activity.

Twenty eight laptops (X50 - X59, X62 - X79), freshly installed with build 703, were booted up sequentially, with 5 seconds between each startup. All laptops managed to join a simple mesh on channel 1, except X73 (Trac ticket 5848, note that this laptop has shown this problem in the past...)

The Write activity was started on laptop X69, and shared with the neighborhood. The shared activity was seen on all laptops immediately.

Seven laptops (X62 - X68) joined the shared activity, almost simultaneously. All of the laptops correctly launched the application, but two laptops (X62 and X63) failed to load the shared document. All other laptops were able to type and have their characters appear on the other laptops.

Logs on X63 were lost due to battery failure. The unit turned off immediately upon unplugging from line power, even though the battery had been charging for weeks. The RF frame logging was conducted with three Active Antennas, separated by one meter, all on channel 1.

Packet Traces: Chan 1(a), Chan 1(b), Chan 1(c)

Laptop X73 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Laptop X62 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Laptop X69 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Test 0321B

Laptop Build: 699 + telepathy-salut-0.2.3-1.olpc2.i386.rpm + Write 55

This test started with 10 laptops (X50 - X59) in a simple mesh on channel 1 (test 0321A had just completed).

The Write activity was started on laptop X54, and shared with the neighborhood. The shared activity was seen on all laptops.

Nine laptops joined the shared activity, almost simultaneously. All of the laptops correctly launched the application and mirrored the shared document. All laptops were able to type and have their characters appear on the other laptops. It was very slow, especially if any characters were erased on any laptop. But it worked!

Packet Traces: Chan 1, Chan 11, Chan 6

Test 0317B

Laptop Build: 699 + Write 55

This test started with 25 laptops (X50 - X74) in a simple mesh on channel 1.

The Write activity was started on laptop X69 (169.254.1.204), and shared with the neighborhood.

The shared activity was seen on 24 of 25 laptops (X70 not showing). After further shared activity, it was eventually seen by all 25 laptops.

Ten laptops joined the shared activity, almost simultaneously. Three of the ten laptops launched write, but never showed the contents of the write document. The other seven correctly mirrored the shared document. The three laptops which failed to collaborate were X51 (169.254.5.153), X53 (169.254.2.7), and X54 (169.254.5.25).

More words were typed on X69, and were mirrored to the seven working laptops (no change in X51, X53, or X54).

Some words were typed on X59, and were correctly mirrored to the seven other collaborating laptops.

Packet Traces: Chan 1, Chan 11, Chan 6

Read Sharing

Test 0331C

Laptop Build: 703 + Read 44

This test booted up 28 laptops in a simple mesh. All laptops successfully joined a simple mesh. A Read activity of a medium sized document (440 KB) was then shared with 5 other laptops. None of them successfully shared the activity.

Twenty eight laptops (X50 - X59, X62 - X79) were booted up sequentially, one every second. All laptops managed to join a simple mesh on channel 1.

The Read activity was started on laptop X69, with a 440KB document, "LED as Sensor.pdf". It was then shared with the neighborhood. The shared activity was seen on all laptops immediately.

Five laptops (X55 - X59) joined the shared activity, almost simultaneously. All of the laptops correctly launched the application, but none of them managed to show the shared document.

The logging was conducted with three Active Antennas, separated by one meter, all on channel 1.

Packet Traces: Chan 1(a), Chan 1(b), Chan 1(c)

Laptop X59 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Laptop X69 logs: All, /var/log/messages, Telepathy/Sugar

Test 0321A

Laptop Build: 699 + telepathy-salut-0.2.3-1.olpc2.i386.rpm + Read 44

This test booted up 10 laptops (X50 - X59). These laptops had been registered with a school server which was not present during the test. All laptops successfully joined the simple mesh on channel 1. All laptops saw one another in their neighborhood view.

The Read activity was started on laptop X59, using a small document (40 KB). The activity was then shared with the neighborhood. The shared activity was seen on all laptops.

An attempt to join the shared Read activity from one laptop (X58) failed. The activity launched, but the document was never displayed.

A later attempt to join the shared Read activity from another laptop (X57) failed. The activity launched, but the document was never displayed.

Packet Traces: Chan 1, Chan 11, Chan 6

Chat

Test 0331B

Laptop Build: 703 + Chat 35

This test booted up 28 laptops in a simple mesh. All laptops successfully joined the simple mesh. A Chat activity was then shared with 10 other laptops. 5 of the 10 successfully shared the activity.

Twenty eight laptops (X50 - X59, X62 - X79) were booted up sequentially, with two laptops started every 5 seconds. All laptops managed to join a simple mesh on channel 1.

The Chat activity was started on laptop X69, and shared with the neighborhood. The shared activity was seen on all laptops immediately.

Ten laptops (X62 - X68) joined the shared activity, almost simultaneously. All of the laptops correctly launched the application, but five of the laptops (X70 - X74) failed show the chat session. X69 showed them as joining the chat. The other five laptops (X75 - X79) were able to type and have their characters appear on each others screen.

X78 behaved abnormally at the beginning. Instead of just announcing each other participant with "Xnn is here", it later announced all of them again with "Xnn joined the chat".

The logging was conducted with three Active Antennas, separated by one meter, all on channel 1.

Packet Traces: Chan 1(a), Chan 1(b), Chan 1(c)

Laptop X74 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Laptop X78 logs: All, /var/log/messages, Telepathy/Sugar

Laptop X69 logs: All, dmesg, /var/log/messages, Telepathy/Sugar

Test 0321C

Laptop Build: 699 + telepathy-salut-0.2.3-1.olpc2.i386.rpm + Chat 35

This test booted up 21 laptops (X50 - X59, X61 - X72). These laptops had been registered with a school server which was not present during the test. Twenty of twenty-one laptops successfully joined the simple mesh on channel 1.

The failing laptop (X65) had no network circle in the home view (Trac 5848), and was rebooted after its logs were captured. It successfully joined the simple mesh. All laptops saw one another in their neighborhood view.

The Chat activity was started on laptop X59. The activity was then shared with the neighborhood (why does Chat have to be shared ? Is OLPC encouraging kids to Chat with themselves ?). Realized that this was done before laptop had joined simple mesh. Stopped activity.

Started Chat activity on laptop X59 again. The activity was then shared with the neighborhood. The shared activity was seen on all laptops.

An attempt to join the shared Chat activity from three laptops (X52, X53, X54) worked. A subsequent attempt to join with the remaining 17 laptops succeeded on all laptops.

All laptops were able to contribute to the conversation, and all laptops saw all characters typed on any laptop. Yahoo!

Packet Traces: Chan 1, Chan 11, Chan 6

Laptop X65 logs: All, dmesg, /var/log/messages, .sugar/default/nm/, Telepathy/Sugar

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox