From: Thomas Pedersen <thomas@cozybit.com>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
Thomas Pedersen <thomas@cozybit.com>
Subject: [PATCH 0/3] implement active mesh scanning
Date: Sat, 2 Feb 2013 17:02:18 -0800 [thread overview]
Message-ID: <1359853341-29237-1-git-send-email-thomas@cozybit.com> (raw)
This set improves the mesh scanning functionality by:
- responding to broadcast or directed probe requests
- allowing the user to generate a directed mesh probe request, ie:
iw mesh0 scan ssid foo
on a mesh interface will send probe requests where the ssid "foo" has
been filled into the mesh ID IE.
Also patch 1 caches the mesh beacon in a struct beacon_data each time it
changes so probe responses can be quickly built. This is also convenient when
the TIM IE becomes needed for PS.
Applies on mac80211-next/master
Thomas Pedersen (3):
mac80211: cache mesh beacon
mac80211: generate mesh probe requests
mac80211: generate mesh probe responses
net/mac80211/cfg.c | 2 +
net/mac80211/ieee80211_i.h | 1 +
net/mac80211/mesh.c | 199 +++++++++++++++++++++++++++++++++++++++++++-
net/mac80211/mesh.h | 3 +
net/mac80211/mesh_plink.c | 6 +-
net/mac80211/rx.c | 5 +-
net/mac80211/tx.c | 72 +++++-----------
net/mac80211/util.c | 1 +
8 files changed, 229 insertions(+), 60 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-02-03 1:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 1:02 Thomas Pedersen [this message]
2013-02-03 1:02 ` [PATCH 1/3] mac80211: cache mesh beacon Thomas Pedersen
2013-02-04 17:37 ` Johannes Berg
2013-02-04 18:09 ` Thomas Pedersen
2013-02-04 18:13 ` Johannes Berg
2013-02-03 1:02 ` [PATCH 2/3] mac80211: generate mesh probe requests Thomas Pedersen
2013-02-04 17:38 ` Johannes Berg
2013-02-04 17:57 ` Thomas Pedersen
2013-02-04 17:58 ` Thomas Pedersen
2013-02-04 18:03 ` Johannes Berg
2013-02-04 18:16 ` Thomas Pedersen
2013-02-03 1:02 ` [PATCH 3/3] mac80211: generate mesh probe responses Thomas Pedersen
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=1359853341-29237-1-git-send-email-thomas@cozybit.com \
--to=thomas@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=johannes@sipsolutions.net \
--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).