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.
This is the second round of patches incorporating the comments from Johannes
Berg and others. The main changes with the first set of patches are:
- We are now using airtime link metric, instead of hop count.
- Mesh peer link table has been discarded, integrating the necessary attributes
directly on struct sta_info.
- We no longer use directily rtnetlink for mesh peer link and mesh paths
operation, and use nl80211 instead.
- We now support mesh network in scan. The part interacting with wext is a bit
ugly but works well. I just read the mail from Johannes with a different
approach and will consider it.
The pid rate control algorithm has been modified to provide an estimated
transmission error, probability, necessary for the airtime link metric, and a to
call mesh_peer_link_broken() if it detects a sta is no longer reachable.
I would like to point out that it looks like we can get duplicate sta_entries,
or more entries than the maximum allowed, if stas are added at the same time
through normal network behaviour and manual operation through nl80211. Please
correct me if I am wrong or if it is just that no interface type is supposed to
allow both kinds of additions.
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.
The patches are to be applied on top of wireless-2.6/everything HEAD. Even
though I am sure there will be some issues, it would be great if we could
integrate this as soon as possible to make it easier for other people to
collaborate and to make my life a bit easier :-)
For more information, please visit: http://o11s.org/devel
Enjoy,
Luis Carlos Cobo
> > > - We no longer use directly rtnetlink for mesh peer link and mesh paths
> > > operation, and use nl80211 instead.
> >
> > Nice too. What does libertas currently do btw?
> >
>
> iwpriv...
eww, ok. Guess we can convert that, CC Dan & David.
> > > I would like to point out that it looks like we can get duplicate sta_entries,
> > > or more entries than the maximum allowed, if stas are added at the same time
> > > through normal network behavior and manual operation through nl80211. Please
> > > correct me if I am wrong or if it is just that no interface type is supposed to
> > > allow both kinds of additions.
> >
> > I think I CC'ed you on the patch fixing that, no?
>
> Not sure which patch are you talking about, anyway I will check that
> along with the mesh + sta_info changes testing.
Subject was "mac80211: atomically check whether STA exists already"
It didn't check the number of STAs since I thought adding one per CPU
more wouldn't hurt too much ;)
johannes