Deployment Guide/Connectivity: Difference between revisions
(See Talk:Deployment_Guide for rationale) |
(add GoogleTrans-en) |
||
| Line 1: | Line 1: | ||
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude> |
|||
==4. Connectivity== |
==4. Connectivity== |
||
Revision as of 20:11, 31 May 2008
Translate this page with Google -español -български -中文（中国大陆） -中文（臺灣） -hrvatski -čeština -dansk -Nederlands -suomi -français -Deutsch -Ελληνικά -हिन्दी -italiano -日本語 -한국어 -norsk -polski -português -română -русский -svenska
4. Connectivity
Although the OLPC ecosystem provides a self-configuring local-area wireless network, connectivity to the Internet is something that needs to be worked out in detail in country. OLPC will assist in the planning and integration of the laptop network to a national infrastructure. We have experience with VSAT, DSL, etc. that we are happy to share. Many of the in-country teams have even more experience than we do, especially in regard to rural deployments. Sharing best practices is in all of our interests. As with the laptop deployment, connectivity will not happen everywhere at once. A phased deployment that runs ahead of the laptop deployment is ideal. Please note that the wireless mesh network provides local “Ethernet”-like connectivity without any additional infrastructure.