Wireless: Difference between revisions
(link to wikipedia 802.11s) |
|||
| Line 25: | Line 25: | ||
=== Mesh wireless === |
=== Mesh wireless === |
||
The Mesh wireless protocol it's an implementation of the 802.11s draft. |
The Mesh wireless protocol it's an implementation of the [http://en.wikipedia.org/wiki/IEEE_802.11s 802.11s draft]. |
||
There is new firmware with mesh routing support: |
There is new firmware with mesh routing support: |
||
| Line 32: | Line 32: | ||
[[Category:OS]] |
[[Category:OS]] |
||
[[Category:Hardware]] |
[[Category:Hardware]] |
||
+++ |
|||
sorry, just a question of an interested reader: |
|||
with the problem of lack of communication infrastructure in these countries olpc seems appealing to me to use as a filler: i envision the use of a lot of these devices to build a mesh... |
|||
(so my question: what is the range of connection free-to-air (outside buildings) to have an idea whether this is feasible..., thanks, thomas |
|||
Revision as of 21:30, 16 November 2006
Network Card
- Marvell 88W8388,
- 802.11b/g compatible;
- Dual adjustable, rotating coaxial antennas;
- Supports diversity reception
Installing Wireless
Tested with Build 76 by Quozl and JvC on OLPC hardware. Verified it still works on Build 81 by Scytacki. rminnich just tested and build 83 works. Teus confirms that build 91 works.
- Attach antennae (so as to prevent damage)
- Obtain the firmware file usb8388_A1_W8015FP14_FW2.bin from https://www.marvell.com/drivers/driverDisplay.do?dId=160&pId=38
- Rename the file to /lib/firmware/usb8388.bin
- Reboot
On builds later than 153 the firmware is already in the image. With build 179 and later NetworkManager with WEP should be working. In those builds all you need to do is click on the wireless strength icon on the upper right hand corner and select your network from the drop down menu. If the device is protected with a WEP key you will be asked to enter it. Subsequent boots of the device should automatically find and associate to the networks it has used before.
The result was that eth0 appeared in ifconfig, and the browser was able to access google.com, thanks to the automatic network configuration.
If you need to setup specific Essids or Keys, look at /etc/sysconfig/network-scripts/ifup-wireless for documentation, and add appropriate variables to ifcfg-eth0
Mesh wireless
The Mesh wireless protocol it's an implementation of the 802.11s draft.
There is new firmware with mesh routing support: https://www.marvell.com/drivers/driverDisplay.do?dId=164&pId=38