linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Carlos Cobo <luisca@cozybit.com>
To: linux-wireless@vger.kernel.org
Subject: [PATCH 00/13 v2] o11s: mesh interface support for mac80211
Date: Thu, 21 Feb 2008 20:05:04 -0800	[thread overview]
Message-ID: <47be76f9.03b48c0a.025f.54f4@mx.google.com> (raw)

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 directly 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 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.

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.

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



             reply	other threads:[~2008-02-22  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  4:05 Luis Carlos Cobo [this message]
2008-02-22 15:21 ` [PATCH 00/13 v2] o11s: mesh interface support for mac80211 Johannes Berg
2008-02-22 15:59   ` John W. Linville
2008-02-22 16:34   ` Johannes Berg
2008-02-23 10:58     ` Johannes Berg
2008-02-25 19:47     ` Luis Carlos Cobo
2008-02-25 19:45   ` Luis Carlos Cobo
2008-02-25 19:50     ` Johannes Berg
2008-02-26  1:03       ` David Woodhouse
2008-02-26  8:22         ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2008-02-22  4:05 Luis Carlos Cobo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47be76f9.03b48c0a.025f.54f4@mx.google.com \
    --to=luisca@cozybit.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).