Collab Network Simple Wifi Tests: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TOCright}}
In these [[Collaboration Network Testbed|collaboration and networking 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.
In these [[Collaboration Network Testbed|collaboration and networking tests]], the laptops are connected through normal 802.11b/g access points (some with, and some without DHCP service). In general, the laptops use peer-to-peer presence and collaboration mechanisms.


Other networking modes tested are [[Collab_Network_Simple_Mesh_Tests|simple mesh]], [[Collab_Network_School_Wifi_Tests|school Wifi]], and [[Collab_Network_School_Mesh_Tests|school mesh]].
Other networking modes tested are [[Collab_Network_Simple_Mesh_Tests|simple mesh]], [[Collab_Network_School_Wifi_Tests|school Wifi]], and [[Collab_Network_School_Mesh_Tests|school mesh]].
Line 15: Line 16:


As the laptops were discovering their network, the "linksys" network was selected from their neighborhood view. Most of the laptops then associated with the AP, and established peer-to-peer collaboration (Salut). Some required a second try. All laptops were able to see one another in their neighborhood view before proceeding.
As the laptops were discovering their network, the "linksys" network was selected from their neighborhood view. Most of the laptops then associated with the AP, and established peer-to-peer collaboration (Salut). Some required a second try. All laptops were able to see one another in their neighborhood view before proceeding.

:See [[12757]] for a possible explanation as to why some laptops required a second try to associate. This bug was present at the time of this test. --[[User:Quozl|Quozl]] 22:49, 11 February 2014 (UTC)


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


'''Packet Traces:''' [http://xs-dev.laptop.org/mesh/test0330/t0330_H_1.dump Chan 10]
'''Packet Traces:''' [http://xs-dev.laptop.org/mesh/test0330/t0330_H_1.dump Chan 10]

[[Category:Network]]

Latest revision as of 22:49, 11 February 2014

In these collaboration and networking tests, the laptops are connected through normal 802.11b/g access points (some with, and some without DHCP service). In general, the laptops use peer-to-peer presence and collaboration mechanisms.

Other networking modes tested are simple mesh, school Wifi, and school mesh.

Chat

Test 0331D

Laptop Build: 703 + Chat 35

Channels: Linksys AP on channel 1, no DHCP

This test booted up 28 laptops, connected using an 802.11b/g WiFi access point. Once connected to the AP, all laptops could detect one another. A shared Chat activity was started, and 8 of the 9 laptops which tried to join the Chat activity succeeded.

Thirty eight laptops (X50 - X59, X62 - X79, X20 - X29) were booted up sequentially, one every second. After the laptops were booted, and searching for a network, ten laptops (X20 - X29) were turned off, as it was remembered that the access point limited tests to thirty laptops.

As the laptops were discovering their network, the "linksys" network was selected from their neighborhood view. Most of the laptops then associated with the AP, and established peer-to-peer collaboration (Salut). Some required a second try. All laptops were able to see one another in their neighborhood view before proceeding.

See 12757 for a possible explanation as to why some laptops required a second try to associate. This bug was present at the time of this test. --Quozl 22:49, 11 February 2014 (UTC)

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

Four laptops (X70 - X73) joined the shared activity, about two second apart. All laptops correctly launched the application, and all but one laptop (X70) joined the Chat.

Five more laptops (X55 - X59) joined the shared activity, about two seconds apart. All laptops correctly joined the Chat. Lines of text were typed on all laptops, and seen on all others (excluding X70).

The logging was conducted with three Active Antennas, separated by one meter, all on channel 1. Logs from X71, a working laptop, were included as well.

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

Laptop X70 logs: All, dmesg pt1, dmesg pt2, /var/log/messages, Telepathy/Sugar

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

Write

Test 0331E

Laptop Build: 703 + Write 55

Channels: Linksys AP on channel 1, no DHCP

This test started with 28 laptops connected using an 802.11b/g WiFi access point. A shared Write activity was started, and 5 of the 10 laptops which tried to join the Write activity succeeded.

Twenty-eight laptops (X50 - X59, X62 - X79) were already connected to a Linksys 802.11b/g access point, using peer-to-peer presence (Salut) from a previous experiment --- all laptops directly involved in the previous experiment were rebooted and re-associated with the "linksys" network.

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

Five laptops (X55 - X59) joined the shared activity, about two second apart. All laptops successfully joined the Write activity. Text typed on several of the laptops could be seen on others.

Five more laptops (X70 - X74) joined the shared activity, about two seconds apart. All laptops successfully launched the Write activity, but never displayed the shared document. After starting these, the already joined laptops (X55 - X59, X69) could no longer collaborate.

The five laptops with failed Write collaboration (X70 - X74) stopped their Write activities. After this, collaboration between the already joined laptops (X55 - X59, X69) resumed.

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 X70 logs: All, /var/log/messages, Telepathy/Sugar

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

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

Test 0330A

Laptop Build: 703 + Write 55

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This test was a test of Write collaboration between two laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Two laptops were turned on, and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

Write was started on Evan (aka 172.24.0.34 aka 00:17:c4:0c:e2:1f), and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b). Clicking on the shared activity launched it, and showed what had been written on Evan so far. Both laptops were able to type, and have it appear on the other, although if one laptop typed really fast, there was a perceptible latency (3-4 sec) before the characters appeared on the other laptop.

The logging was conducted with one Active Antenna.

Packet Traces: Chan 10

Test 0330C

Laptop Build: 703 + Write 55

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This test was a test of Write collaboration between three laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Four laptops (Betty, Charlie, Daniel, and Evan) were turned on, and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

A fifth laptop, Adrian, was turned on. Adrian associated fine with the Watlington network when it was clicked on, but did not show the other laptops. After turning on the Sugar log files, Sugar was restarted on Adrian.

Write was started on Evan (aka 172.24.0.34 aka 00:17:c4:0c:e2:1f), and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b) and Betty (172.24.0.39 aka 00:17:c4:0d:42:b0) launched the shared activity by clicking on it, and showed what had been written on Evan so far. All laptops were able to type, and have it appear on the other laptops.

The logging was conducted with one Active Antenna.

Packet Traces: Chan 10

Test 0330D

Laptop Build: 703 + Write 55

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This was a successful test of Write collaboration between six laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Seven laptops (Adrian, Betty, Charlie, Daniel, Evan, Ian, and Nathan) were turned on and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

Write was started on Evan (aka 172.24.0.34 aka 00:17:c4:0c:e2:1f), and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b), Betty (172.24.0.39 aka 00:17:c4:0d:42:b0), Charlie, and Ian launched the shared activity by clicking on it, and showed what had been written on Evan so far. All laptops were able to type, and have it appear on the other laptops. Daniel joined the activity late, with success.


The logging was conducted with one Active Antenna. The traces were started when some of the laptops were just starting up.

Packet Traces: Chan 10

Measure

Test 0330B

Laptop Build: 703 + Measure 15

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This test was a test of Measure collaboration between two laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Two laptops were turned on, and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

Measure was started on Evan (aka 172.24.0.34 aka 00:17:c4:0c:e2:1f), and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b). Clicking on the shared activity launched it. After clicking on Begin Measurement on both laptops, the laptops correctly calculated the distance between them for a minute before being stopped.

The logging was conducted with one Active Antenna.

Packet Traces: Chan 10

Read

Test 0331F

Laptop Build: 703 + Read 44

Channels: Linksys AP on channel 1, no DHCP

This test started with 28 laptops connected using an 802.11b/g WiFi access point. A shared Read activity was started with a medium sized document (440 KB). One of the four laptops which tried to join the Read activity succeeded within an acceptable time period. Another laptop succeeded after several minutes.

Twenty-eight laptops (X50 - X59, X62 - X79) were already connected to a Linksys 802.11b/g access point, using peer-to-peer presence (Salut) from a previous experiment --- all laptops directly involved in the previous experiment were rebooted and re-associated with the "linksys" network.

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

The shared activity was joined by two laptops (X62, then X74). X62 succeeded in loading the shared document within a minute.

The shared activity was then joined by another two laptops (X58, X59). Neither of these succeeded in loading the shared document.

X74 succeeded in loading the shared document after several minutes, after the packet trace had been halted but before its logs were copied.

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, /var/log/messages, Telepathy/Sugar

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

Test 0330E

Laptop Build: 703 + Read 44

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This was an unsuccessful test of large sized (2.2MB) document Read collaboration between seven laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Seven laptops (Adrian, Betty, Charlie, Daniel, Evan, Ian, and Nathan) were turned on and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

The Read activity was started on Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b) with a 2.2MB PDF, and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. all of the other laptops launched the shared activity by clicking on it, several seconds apart from one another. None of the laptops were able to successfully load the shared document.

The logging was conducted with one Active Antenna. The traces were started when some of the laptops were just starting up.

Packet Traces: Chan 10

Adrian's logs: All, /var/log/messages, Telepathy/Sugar

Betty's logs: All, /var/log/messages, Telepathy/Sugar

Daniel's logs: All, /var/log/messages, Telepathy/Sugar

Test 0330F

Laptop Build: 703 + Read 44

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This was an somewhat successful test of small sized (40 KB) document Read collaboration between seven laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Seven laptops (Adrian, Betty, Charlie, Daniel, Evan, Ian, and Nathan) were turned on and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

The Read activity was started on Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b) with a 40 KB PDF, and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. Betty launched the activity successfully. Charlie, Daniel, Evan, Ian, and Nathan then launched the shared activity. All but Charlie were successful in opening the shared document.

Read was stopped on Charlie (after obtaining the logs) and another attempt to join the shared activity made. This time, Charlie was able to read the shared document.

The logging was conducted with one Active Antenna. The traces were started when some of the laptops were just starting up.

Packet Traces: Chan 10

Charlie's logs: All, /var/log/messages, Telepathy/Sugar

Test 0330G

Laptop Build: 703 + Read 44

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This was a successful test of medium sized (440 KB) document Read collaboration between seven laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Seven laptops (Adrian, Betty, Charlie, Daniel, Evan, Ian, and Nathan) were turned on and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

The Read activity was started on Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b) with a 440 KB PDF, and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. Betty launched the activity successfully. Charlie, Daniel, Evan, Ian, and Nathan then launched the shared activity. All were successful in opening the shared document.

The logging was conducted with one Active Antenna. The Active antenna jammed up and aborted the trace before the test was finished. In /var/log/messages, the message was:

libertas: Command 28 timed out
libertas: requeing command 28 due to timeout (#1)
libertas: Command 28 timed out
libertas: requeing command 28 due to timeout (#2)

Packet Traces: Chan 10

Test 0330H

Laptop Build: 703 + Read 44

Channels: Airport AP on channel 10, DHCP

This test was not performed at the Collaboration Networking Testbed, but in a similarly quiet RF environment.

This was a successful test of medium sized (440 KB) document Read collaboration between seven laptops, connected through a WiFi access point. No school server was accessible through the access point (although one was running on channel 1).

Seven laptops (Adrian, Betty, Charlie, Daniel, Evan, Ian, and Nathan) were turned on and the "Watlington" network was selected from their neighborhood view. Each laptop saw the other in their neighborhood view.

The Read activity was started on Adrian (aka 172.24.0.38 aka 00:17:c4:0c:e2:8b) with a 440 KB PDF, and shared with the neighborhood. The shared activity was immediately visible in the neighborhood view of the other laptops. All other laptops launched the shared activity within a couple of seconds of one another. All were successful in opening the shared document.

The logging was conducted with one Active Antenna.

Packet Traces: Chan 10