Stuffed Crust wrote:
On Mon, Jan 16, 2006 at 09:54:15AM -0800, Sam Leffler wrote:
The way you implement bg scanning is to notify the ap you are going into
power save mode before you leave the channel (in sta mode). Hence bg
scanning and power save operation interact.
That is not "powersave operation" -- that is telling the AP we are going
into powersave, but not actually going into powersave -- Actual
powersave operation would need to be disabled if we go into a scan, as
we need to have the rx path powered up and ready to hear anything out
there for the full channel dwell time.
Please read what I wrote again. Station mode power save work involves
communicating with the ap and managing the hardware. The first
interacts with bg scanning. We haven't even talked about how to handle
sta mode power save.
See above. Doing bg scanning well is a balancing act and restoring
hardware state is the least of your worries (hopefully); e.g. what's the
right thing to do when you get a frame to transmit while off-channel
scanning, how often should you return to the bss channel?
Disallow all other transmits (either by failing them altogether, or by
buffering them up, which I think is better) while performing the scan.
Not necessarily in my experience.
If we are (continually) scanning because we don't have an association,
then we shouldn't be allowing any traffic through the stack anyway.
If you do not have an association you are not doing bg scanning.
At the end of each scan pass, you return to the original channel, then
return "scan complete" to the stack/userspace. at this point any
pending transmits can go out, and if another scan pass is desired, it
will happen then.
If you wait until the end of the scan to return to the bss channel then
you potentially miss buffered mcast frames. You can up the station's
listen interval but that only gets you so far. As I said there are
tradeoffs in doing this.
Er, you need to listen to at least beacons from other ap's if you're in
11g so you can detect overlapping bss and enable protection. There are
other ways to handle this but that's one.
If you can't hear the traffic, then it doesn't count for purposes of ER
protection -- but that said, this only matters for AP operation, so APs
shouldn't filter out anyone else's becacons. STAs should respect the
"use ER Protection" bit in the AP's beacon, so can filter out traffic
that doesn't match the configured BSSID.
Sorry I meant this was needed for ap operation.
Oh, I know. I've burned out many brain cells trying to build
supportable solutions for our customers.
I don't recall seeing well-developed scanning code in either of the
proposed stacks.
I've only looked into the pre-2.6-merged HostAP stack, so I can't
comment on what's publically available. I'll have a look at the GPL'ed
DeviceScape stack when I have more time.
Most of what I've going on about is derived from my experience from
commercial 802.11 work I've done over the past few years.
Ditto.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
