> 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. Cool. > - Mesh peer link table has been discarded, integrating the necessary attributes > directly on struct sta_info. Neat. I'll have to respin either my recent sta_info reorg patches or these. I can do the work either way, sorry for messing with mac80211 all the time. > - 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? > - 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. I'll take a look here too. > 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. Interesting. Would like to get Stefano's input on that. > 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? > The code has been tested in a 12-node testbed and has proved to be stable and > functional. 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. I think b43 should be fine since it supports AP (so clearly beacons), the only thing to figure out is whether to turn on or off INFRA mode (ie. use AP or IBSS beaconing) > 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 :-) Hm. I think you'd have to rebase on top of wireless-testing/master but I'm not sure how they currently differ. See John Linville's mail on the new tree structure. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
