Mesh OLPC Testbed: Difference between revisions
No edit summary |
m (Reverted edits by 67.223.234.160 (Talk) to last version by Carrano) |
||
| (5 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
ricormon |
|||
{{OLPC}} |
{{OLPC}} |
||
{{obsolete}} |
|||
=== 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. |
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. |
||
A [[Collaboration Network Testbed|second testbed]] has also been established in the Boston area for larger scale testing of both collaboration and networking. |
|||
The prototype schoolserver has three mesh interfaces, one on each channel the OLPC mesh uses (1, 6, and 11). It acts as a mesh portal point (MPP) on each mesh subnet, routing between them and the Internet. The schoolserver assigns private addresses (172.18.16.0/20,172.18.32.0/20, and 172.18.48.0/20) to the laptops on each mesh subnet using DHCP, and masquerades traffic outgoing from the mesh to the Internet. |
The prototype schoolserver has three mesh interfaces, one on each channel the OLPC mesh uses (1, 6, and 11). It acts as a mesh portal point (MPP) on each mesh subnet, routing between them and the Internet. The schoolserver assigns private addresses (172.18.16.0/20,172.18.32.0/20, and 172.18.48.0/20) to the laptops on each mesh subnet using DHCP, and masquerades traffic outgoing from the mesh to the Internet. |
||
| Line 44: | Line 46: | ||
| --[[User:Wad|Wad]] 22:47, 12 April 2007 (EDT) || 4 hours || nodes 20 and higher |
| --[[User:Wad|Wad]] 22:47, 12 April 2007 (EDT) || 4 hours || nodes 20 and higher |
||
|- |
|- |
||
| --[[User:Jcardona|Jcardona]] 22:04, 8 March 2008 (EST) || 2 hours || meshy1 and 2 |
|||
|- |
|||
|} |
|} |
||
Latest revision as of 07:07, 17 December 2008
This page has a more up-to-date location: {{{link}}}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.
A second testbed has also been established in the Boston area for larger scale testing of both collaboration and networking.
The prototype schoolserver has three mesh interfaces, one on each channel the OLPC mesh uses (1, 6, and 11). It acts as a mesh portal point (MPP) on each mesh subnet, routing between them and the Internet. The schoolserver assigns private addresses (172.18.16.0/20,172.18.32.0/20, and 172.18.48.0/20) to the laptops on each mesh subnet using DHCP, and masquerades traffic outgoing from the mesh to the Internet. We ask that you not establish additional 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 |
| --Wad 22:47, 12 April 2007 (EDT) | 4 hours | nodes 20 and higher |
| --Jcardona 22:04, 8 March 2008 (EST) | 2 hours | meshy1 and 2 |
Activity Log
--Wad 11:04, 13 April 2007 (EDT) Nodes 10, 19, 20, 23, 24, and 25 are no longer receiving a DHCP lease on their wired interface, and are also temporarily out of commission. Rebooting does not help.
--Wad 22:42, 12 April 2007 (EDT) Meshy7 (18.85.46.134) is down and out for the count. I powered it off until someone can fix it. The firmware on all laptops is now 5.220.10.p5 (I did not change this.) By default, the mesh interfaces are not configured properly to access the schoolserver.
--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)