#612: [patch] Fix channel switch while in monitor mode.
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: dyqith
Type: defect | Status: reopened
Priority: major | Milestone: version 0.9.x -
progressive release candidate phase
Component: madwifi: 802.11 stack | Version: trunk
Resolution: | Keywords: channel switch
monitor wds
Patch_attached: 1 |
---------------------------------------------+------------------------------
Changes (by [EMAIL PROTECTED]):
* resolution: invalid =>
* status: closed => reopened
Comment:
At least in my case the ic->ic_bsschan field sometimes contains a pointer
to a valid channel description structure, even when the vap is running in
monitor mode.
This field is not zeroed out when it should be invalid, so it may contain
old information. This causes the check to evaluate to true and ignore a
channel change, even when it should always change because it is in monitor
mode.
In my case it frequently happens when I use kismet. Normally the card has
one VAP running in ad-hoc mode on channel 40 (Mode a). When kismet starts
it creates a monitor VAP and scans the channels 40,52 and 64. But because
it was previously in channel 40 the ic_bsschan field still contains
channel 40 and makes it impossible for kismet to switch to channel 40.
--
Ticket URL: <http://madwifi.org/ticket/612>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
