Mesh OLPC Testbed: Difference between revisions
(Added request to not setup additional portal in the lab without warning) |
|||
| Line 1: | Line 1: | ||
{{OLPC}} |
|||
=== Mesh OLPC Testbed === |
=== Mesh OLPC Testbed === |
||
| ⚫ | In OLPC's Cambridge lab there is a set of XO laptops dedicated to testing the mesh network. Currently there are 25 laptops and a school server in this testbed. In addition to their mesh network interface, all the laptops are connected to the Internet via a [http://www.dlink.com/products/?sec=1&pid=133 USB ethernet adapter]. You can do things like reloading the driver/firmware of the wireless interface, scanning/associating to access points, etc. |
||
This is a mesh of 25 xo's that are dedicated to run mesh tests. |
|||
| ⚫ | |||
We ask that you not establish additional mesh portal points (MPPs) without discussing it first with us. Send mail to <i>wad at laptop dot org</i> or <i>mbletsas at laptop dot org</i>. |
|||
=== Testbed Reservation System === |
=== Testbed Reservation System === |
||
Revision as of 02:23, 13 April 2007
Mesh OLPC Testbed
In OLPC's Cambridge lab there is a set of XO laptops dedicated to testing the mesh network. Currently there are 25 laptops and a school server in this testbed. In addition to their mesh network interface, all the laptops are connected to the Internet via a USB ethernet adapter. You can do things like reloading the driver/firmware of the wireless interface, scanning/associating to access points, etc.
We ask that you not establish additional mesh portal points (MPPs) without discussing it first with us. Send mail to wad at laptop dot org or mbletsas at laptop dot org.
Testbed Reservation System
Book exclusive use of the OLPC testbed here.
Procedure:
1. Check/edit this page before beginning to use the OLPC testbed.
2. To reserve, paste the following line at the bottom of the table below:
| --~~~~ || 1 hour || all nodes |-
3. Edit according to your needs
| who, start time | duration | number of nodes |
|---|---|---|
| --Jcardona 15:31, 7 March 2007 (EST) | 5 hours | all nodes |
| --Jcardona 21:50, 7 March 2007 (EST) | 48 hours | all nodes (working on #1005) |
| --Jcardona 22:26, 19 March 2007 (EDT) | 24 hours | all nodes |
| --Jcardona 17:55, 22 March 2007 (EDT) | 2 hour | 1 and 2 |
| --Luisca 13:04, 28 March 2007 (EDT) | 24 hours | all nodes |
| --Wad 10:26, 12 April 2007 (EDT) | 10 hours | all nodes |
Activity Log
--Jcardona 19:27, 9 March 2007 (EST) Upgraded firmware to development image 5.220.9p254. fwt_list will return invalid results until the driver is upgraded.
--Jcardona 22:26, 19 March 2007 (EDT) Upgraded firmware to development release candidate image 5.220.9.p247 on all nodes except 2 (it was down)
--Jcardona 17:58, 22 March 2007 (EDT) Crashed meshy1. rmmod driver without bringing down interface ( http://dev.laptop.org/ticket/992 )
--Jcardona 22:20, 23 March 2007 (EDT) Upgraded firmware to development image 5.220.10p2 on meshy3
--Luisca 19:10, 29 March 2007 (EDT) Upgraded firmware to development image 5.220.10.p4 on all nodes (meshy1 to meshy 18)