[PATCH 00/13] o11s: mesh interface support for mac80211

[Luis Carlos Cobo <luisca@cozybit.com>]

This series of patches provides support for (pre) IEEE 802.11s mesh interfaces.
Current features include mesh discovery, peer link establishment and on-demand
HWMP path discovery, using hop count as the metric.

The code has been tested in a 12-node testbed and has proved to be stable and
functional. We would like to get it integrated as soon as possible so it can get
more widespread testing and (hopefully) contributions. Unfortunately we have run
out of funds for this project (we are looking for sponsors!) so work on the
project from our side might slow down. At the very least, we are commited to
fixing bugs and tracking changes introduced by newer versions of the 11s draft.

The only supported driver right now is zd1211rw, but changes in the driver for
mesh functionality are minimal (for the zd1211rw driver most changes were just
to provide missing functionality such as beaconing support), so we expect a wide
array of devices to be supported soon.

We would appreciate any comments or advice useful toward integration of this
code. Specific areas where we would like to get some feedback are:

- Possible integration between mesh peer link and sta_info structures. Their
  purpose is similar and it will make it easier to implement mesh rate control
  and airtime link metric.

- Beaconing support: the current beacon model is appropriate for the zd1211rw
  driver but might not be for others.

- set_mesh_cfg command to set mesh ID and use of broadcast mesh ID when none is
  set: Johannes suggested the mesh ID should be specified when creating the mesh
  interface [1]. However we feel that a "mesh configuration" or "mesh network"
  object analogous to the "association" object he talks about would be more
  appropriate. Such an association object has not yet been implemented. We
  would appreciate some advice on how to implement our mesh network object so
  that it follows the spirit of mac80211.

- Scan support: we were waiting for scan to be moved to cfg80211 to avoid
  messing unnecessarily with wext, is there any effort in this direction?

[1]: http://www.spinics.net/lists/linux-wireless/msg07745.html

For more information, please visit: http://o11s.org/devel

Enjoy,

Luis Carlos Cobo