From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: Javier Cardona <javier@cozybit.com>, linux-wireless@vger.kernel.org
Subject: [PATCH 0/5] mesh improvements
Date: Fri, 03 Dec 2010 09:20:39 +0100 [thread overview]
Message-ID: <20101203082039.131181927@sipsolutions.net> (raw)
Ok so this is the final versions of the mesh
patches we've been working on.
I replaced my first patch with Javier's, so
that we no longer hardcode any TTL but the
element TTL is also configurable.
Now you can join/leave meshes on the fly, and
we can work on adding more setup to creating
the mesh, like the beacon IEs Javier had an
interest in. Another easy target would be the
beacon interval, for example.
I think eventually this should be extended a
bit further in that drivers would need the
ability to advertise which of the mesh config
parameters they support. mac80211 currently
supports all of them, but I could see that
change with newer drafts, and I can also see
not all devices (like libertas...) supporting
all possible parameters.
johannes
next reply other threads:[~2010-12-03 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 8:20 Johannes Berg [this message]
2010-12-03 8:20 ` [PATCH 1/5] nl80211/mac80211: define and allow configuring mesh element TTL Johannes Berg
2010-12-03 8:20 ` [PATCH 2/5] mac80211: move mesh filter adjusting Johannes Berg
2010-12-03 8:20 ` [PATCH 3/5] cfg80211: require add_virtual_intf to return new dev Johannes Berg
2010-12-03 8:20 ` [PATCH 4/5] nl80211: refactor mesh parameter parsing Johannes Berg
2010-12-03 8:20 ` [PATCH 5/5] cfg80211/mac80211: add mesh join/leave commands Johannes Berg
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=20101203082039.131181927@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).