Mesh Network FAQ/lang-es

  Esta página está supervisada por el equipo de OLPC.

english | español

HowTo [ID# 142849]  +/-

Ahora, edita tu traducción, usando lo siguiente como guía: [[Original page]] [[Original page/lang-es]] (nombre de la página traducida) Borrando el texto traducido... (no muy recomendado) {{OLPC}} {{Translations}} == Some header == Some text blah... blah... [[#Another header]] ... blah == Another header == Some other text blah... blah... [[Another page]] and [[Another page#section|section]] ... blah {{OLPC}} {{Translation | lang = xx | source = Original page | version = yyyy}} {{Ongoing Translation}} {{anchor|Some header}} == Un titular == Algo de texto bla... bla... [[#Another header|Otro titular]] ... blah {{ Translated text | Some text blah... blah... [[#Another header]] ... blah | display = block}} {{anchor|Another header}} == Otro titular == Algo más de texto bla... bla... [[Another page/lang-xx|Otra página]] y [[Another page/lang-xx#section|sección]] ... bla {{ Translated text | Some other text blah... blah... [[Another page]] and [[Another page#section|section]] ... blah | display = block}} {{OLPC}} {{Translation | lang = xx | source = Original page | version = yyyy}} {{anchor|Some header}} == Un titular == Algo de texto bla... bla... [[#Another header|Otro titular]] ... blah {{anchor|Another header}} == Otro titular == Algo más de texto bla... bla... [[Another page/lang-xx|Otra página]] y [[Another page/lang-xx#section|sección]] ... bla Páginas de soporte: si hay un enlace rojo como el siguiente: [[Original page/translations]] [[Original page|english]] [[Original page/lang-es|Página original]] ... debes seguirlo y pegar "{{subst:requesttranslation}}" allí: [[Another page/lang-es]] [[Another page]] {{subst:requesttranslation}} Eso se sustituye con el template: ''{{Translation|lang=es|source=Another page|status=deseada}} some untranslated page... maybe the content is mutating rapidly, or is peripheric to the main corpus, etc.

This is an on-going translation

Estas son preguntas sobre la Red Mesh usada por el laptop XO. Una página relacionada es Detalles de la red Mesh.

These are questions about the Mesh Network used by the XO laptop. A related page is Mesh Network Details.

Cuántos servidores por escuela?

Cómo estarán conectados los servidores de escuelas en una escuela, y cuántos usuarios se espera que soporten?

Actualmente se planea que la relación de estudiantes a servidores de escuela no sea más de 100:1. La interconección entre servidores será la mejor posible: se recomienda fuertemente Cat3/5 o línea de poder, con inalámbrica como respaldo si es necesario.

Cada servidor soportará por lo menos dos puntos de acceso WiFi (los módulos Marvell), con hasta cinco o seis puntos de acceso posibles. El escenario óptimo de despliegue probablemente provee dos o tres redes mesh por escuela (en los canales 11, 1 y 6). Cada servidor provee puntos de acceso en dos o más redes mesh (por ej. si hay múltiples servidores/puntos de acceso en cada mesh.)

How will the school servers in one school be connected, and how many users each are they expected to support?

The ratio of students to school servers is currently planned to be no more than 100:1. The interconnection between servers will be best possible: Cat3/5 or powerline is strongly recommended, with a fallback to wireless if necessary.

Each server will support at least two WiFi access points (the Marvell modules), with up to five or six access points possible. The optimum deployment scenario probably provides two or three meshes per school (on channels 11, 1, and 6). Each server provides access points on two or more meshes (i.e. there are multiple servers/access points on each mesh.)

Cómo se elige el canal de mesh para un unir un laptop?

Debe pasar algún tiempo en cada canal y estimar cuan pesado es el tráfico de paquetes RREQ y RREP.

Ésto es complicado, ya que estos paquetes nos de envían al host. Una manera de determinarlo indirectamente es examinar la tabla de forwarding: cuando se reciben RREQs, se crean rutas reversas. Alternativamente, uno podría monitorear las estadísticas de forwarding de la interfaz mesh (ethtool -S msh0). Estos son todos métodos de detección "pasivos": no funcionará si todos los hosts en la mesh están callados.

Otro método alternativo sería correr demonios sobre la interfaz de mesh, tales como http://www.cozybit.com/projects/lsmesh

La respuesta a esto ahora esta dada por los Detalles de la red Mesh

:You have to spend some time on every channel and estimate how heavy the traffic is from the RREQ and RREP packets.

This is tricky, as these packets are not sent to the host. One way to determine this indirectly is to examine the forwarding table: when RREQs are received, reverse routes are created. Alternatively, one could monitor the forwarding statistics of the mesh interface (ethtool -S msh0). These are all "passive" detection methods: will not work if all the hosts in the mesh are silent.

Yet another alternative would be to run daemons attached to the mesh interface, such as http://www.cozybit.com/projects/lsmesh

This is now answered by the Mesh Network Details

How can we determine whether a channel has other active mesh users?

There are no beacons currently (although they are in the implementation plan) so you really have to listen for mesh traffic.

How many radios can one mesh channel support?

How will a laptop decide to join another mesh channel if the current one gets too busy?

Is there an answer ?

Is the XO-1 Laptop Mesh atennea limited to aprox 24 connections before bad collisions, similar to regular WiFi technology ? --iainD 21:28, 16 January 2008 (EST)

Will physically adjacent laptops be on the same mesh ?

Is it possible that two children sitting next to one another are on different channels and therefore cannot "see" each other on the net?

One of the roles of the School server will be to bridge between mesh clouds running on different channels. How do you decide what mesh (channel) to join was a previous question.

What about WiFi encryption ?

Does the mesh part of the firmware use the same encryption settings as the b interface? Do we care about making a 'private mesh' with WPA-PSK or WEP or something like that?

Yes, the mesh uses the same encryption.

Down the road, we care, and will probably use WPA-PSK.--Michalis

I will argue that link layer encryption is the wrong place to protect secrets. If an application handles private or sensitive data, it should apply encryption at that time (e.g. HTTPS). My concern is the management overhead of the authentication server for WPA-PSK. The ability of devices other than XO laptops to join the school network will be supported. --Wad 00:21, 22 February 2007 (EST)

______________________________________________________________________________________________________________________________________ I read here which WPA(PSK) can work for mesh network but it is a several days that i am trying to configure the PWA(PSK) for mesh network in OpenWrt, i did not get result, and also gave a message that shows " WPA(PSK) does not support ad-hoc network. if some one know that how can apply the WPA(PSK) on ad-hoc network please inform me, my E-mail: salimsaay@gmail.com

How are school servers (network gateways) discovered?

Will servers send out some sort of announcements to allow the laptops to find them automatically, or must we cache a DNS name or IP address for the server?

They will act as gateways and respond to RREQs for a reserved anycast address.--Michalis

This is two different questions. At the layer 2 networking level, the laptop is looking for a default gateway. This will be supplied by a mesh network configuration server running on all school servers, which responds to a request for a particular anycast address with its IP address. The laptop will then use DHCP to request an IP address, netmask, domain name servers, and default domain.

At the services level, each laptop will be associated with a particular school server that contains a student's journal and backups, through a mechanism which is still being defined.--Wad