On this page... (hide)

  1.   1.  SSID(s)
  2.   2.  Routing Protocol
  3.   3.  Addressing
  4.   4.  Network coordinator

This is a draft document, and not a final standard.

The document details the standards for nodes in the Buffalo Mesh network. In this document, IP address configuration, SSID's, and any security mechanisms present in the routing protocols will be annotated.

While anyone is free to configure their nodes in any manner desired, in order for inclusion as part of this particular network, certain standards must be met in order to ensure inter-operability and routing.

1.  SSID(s)

The backbone SSID of the nodes is BACKBONE-BMN, and this SSID is an ad-hoc network operating on channel 35. Antennas may be directional in order to facilitate longer links, or unidirectional to support all neighboring nodes. However, if your links will be passing over/through any local meshes, a different SSID may be required, in order to reduce interference. In outlying areas, 2.4GHz backbone channel of 11 can be used, however, this should be avoided when possible.

The client-access SSID should be set to, preferably on Channel 1, although channel 6 might be more appropriate given local network activity. Channel 11 should never be used, as to keep the reserve backbone channel as clear as possible. This serves as one common name, that allows client devices to understand who is providing the service to them, and acts as a sort of built-in book mark, so interested parties can quickly find more information about the network they are participating in.

Local mesh ad-hoc network SSID's can also be used, but special care must be taken to actually add sufficient bridge nodes into the BACKBONE-BMN SSID.

If you are planning a long-link, please consult with the network coordinator. He or she will be able to offer guidance into what hardware to use, which nodes would be best to long-link with, channel allocation, and SSID to use.

2.  Routing Protocol

While still open to testing, and improvement, the current standard for mesh network routing is OLSR (Optimized Link State Routing), and much work to bring this protocol to commodity hardware has been done already, thereby bootstrapping this into all of the common OS's.

All nodes shall be running OLSR on the Wireless backbone interfaces, and preferably the Commotion Wireless firmware.

3.  Addressing

Commotion Wireless firmware handles auto-configuration of IP addressing for all interfaces of the radios.

4.  Network coordinator

The network coordinator shall be named as soon as feasible, and the goal is to have as-required elections to vote in the best coordinator for the time.

The job of the network coordinator is pretty simple: To herd cats. A coordinator cannot order specific node owners to do anything. Node owners own their hardware. So, the job of the coordinator comes down to making decisions, demonstrating they are the best decisions for the long term, and work with individuals to get those decisions into practice. That being said, if a node owner refuses to abide by the network standards, that node will not be considered a member of this network, and can be shunned. Shunning a network will route any traffic from said network into a routing black hole, to prevent wide-spread disruption.

Page last modified on November 11, 2014, at 08:26 PM