Stuffed Crust wrote:
On Sun, Jan 15, 2006 at 11:53:55AM -0800, Sam Leffler wrote:
The above is a great synopsis but there is more. For example to support
roaming (and sometimes for ap operation) you want to do background
scanning; this ties in to power save mode if operating as a station.
Opportunistic roaming is one of those things that has many knobs to
twiddle, and depends a lot on the needs of the users.
But we're not actually in powersave mode -- the 802.11 stack can spit
out the NULL frames to tell the AP to buffer traffic for us. This is
trivial to do.
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.
Scans should be specified as "non-distruptive" so the hardware driver
has to twiddle whatever bits are necessary to return the hardware to the
same state that it was in before the scan kicked in. Beyond that, the
scanning smarts are all in the 802.11 stack. The driver should be as
dumb as possible. :)
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?
Background scanning, yes -- but there are all sorts of different
thresholds and types of 'scanning' to be done, depending on how
disruptive you are willing to be, and how capable the hardware is. Most
thin MACs don't filter out foreign BSSIDs on the same channel when
you're joined, which makes some things a lot easier.
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.
Further you want to order your channel list to hit the most likely
channels first in case you are scanning for a specific ap--e.g. so you
can stop the foreground scan and start to associate.
With my scenarios, the driver performs the sweep in the order it was
given -- if the hardware supports it, naturally.
Channel ordering is useful no matter who specifies it. If you offload
the ordering to the upper layers then they need to be aware of the
regdomain constraints. Probably not a big deal but then you need to
synchronize info between layers or export it. And there's other
regdomain-related info that may want to be considered such as max
txpower. I'm just saying if you want to do a good job there's lots of
work here.
In terms of beacon miss processing some parts have a hardware beacon
miss interrupt based on missed consecutive beacons but others require
you to detect beacon miss in software. Other times you need s/w bmiss
detection because you're doing something like build a repeater when
the station virtual device can't depend on the hardware to deliver a
bmiss interrupt.
Of course. The stack is going to need a set of timers regardless of the
hardware's capabilities, but having (sane) hardware beacon miss
detection capabilities makes it a bit more robust.
Scanning (and roaming) is really a big can 'o worms.
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.
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]
