Differences between revisions 10 and 11
Revision 10 as of 2005-03-16 06:49:29
Size: 1663
Editor: WikiMinion
Comment:
Revision 11 as of 2007-10-27 14:46:13
Size: 1537
Editor: adsl-75-37-11-156
Comment: wording
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * The ESSID should be set to www.personaltelco.net and WEP turned off, to allow mobile users to connect to any of the WirelessNeighborhoods without changing settings. This is a primitive form of "roaming" which is goog enough in nearly every occasion because most software uses very short bursts of connection (e.g, a webbrowser) or will rebuild a connection as soon as it discovers that it was lost. It's doesn't to allow seamless transition from one to another however.  * The ESSID should be set to www.personaltelco.net and WEP turned off, to allow mobile users to connect to any of the WirelessNeighborhoods without changing settings. This is a form of low-quality "roaming" which does not allow seamless transition from one coverage zone to another but, on most laptops will rebuild a connection as when possible.

A WirelessNeighborhood is a local geographic collection of WirelessNetworking participants directly connected with each other. Typically, one fixed location serves as a "hub", with an omnidirectional antenna and AccessPoint that the other members are able to see and link up to as "client" nodes. This is usually achieved by having clear LineOfSight to the central antenna and aiming a directional antenna at it, connected to a client device. In addition to the fixed nodes, mobile users can usually connect within a short distance of a central antenna, such as a laptop at the coffee shop down the block.

There are a few standards that have been agreed upon informally for WirelessNeighborhoods:

  • The ESSID should be set to www.personaltelco.net and WEP turned off, to allow mobile users to connect to any of the WirelessNeighborhoods without changing settings. This is a form of low-quality "roaming" which does not allow seamless transition from one coverage zone to another but, on most laptops will rebuild a connection as when possible.

  • IP address space and Internet routing (and funding) are up to the WirelessNeighborhood, but at the least should have a basic firewall router separating the wireless segment from the local LAN and Internet connection. Hopefully, we can one day share a common CaptivePortal system that we can run from a self-booting Linux router disk or similar.

A WirelessNeighborhood may be connected to other WirelessNeighborhoods within a WirelessCommunity.


[CategoryGlossary]

WirelessNeighborhood (last edited 2007-11-23 18:02:15 by localhost)