From: Andy Green <andy@warmcat.com>
To: linux-wireless@vger.kernel.org
Subject: Faking powersave for fun and realtime channel muxing
Date: Mon, 19 Mar 2007 19:57:40 +0000 [thread overview]
Message-ID: <45FEEB34.1000403@warmcat.com> (raw)
Hi folks -
If you could generate and manage powersave protocol frames to an AP from
the mac80211 stack, without actually putting the radio to sleep, you
could do some interesting things.
For example you could allow any logical network interface to have a
different channel. In this case, during the time that the channel you
are associated on has been told you have gone into powersave mode, you
can actually spend time on that other channel, before switching the
channel back to check in with the AP. So you could for example run
monitor mode on channel 11 while being associated on channel 2, given
the limitation that sometimes you aren't listening because you are
taking care of business on channel 2. This can surely lead to ripping
out all the "scanning" stuff and ioctl(s) from kernel mode and doing it
from a regular interface using the existing Monitor semantics.
Depending on the limitations of the time you can arrange to "sleep" with
the AP, using this technique you could even associate multiple logical
interfaces to APs on different channels despite they are sharing one
physical radio. That could be cool for dealing with realtime selection
of the best channel/AP when the guy is mobile, for example.
Is there something like firmware constraints or the detail of the
powersaving protocol that kill this dead or is it possible to consider?
-Andy
next reply other threads:[~2007-03-19 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 19:57 Andy Green [this message]
2007-03-19 20:08 ` Faking powersave for fun and realtime channel muxing Michael Buesch
2007-03-19 20:52 ` Andy Green
2007-03-20 17:48 ` James Ketrenos
2007-03-19 20:38 ` Michael Wu
2007-03-19 21:16 ` Andy Green
2007-03-21 15:24 ` Jiri Benc
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=45FEEB34.1000403@warmcat.com \
--to=andy@warmcat.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).