Hi Peter,
On Wednesday 30 November 2011 08:06 AM, Peter Stuge wrote:
Mohammed Shafi Shajakhan wrote:
before concluding that the recieved beacon is for us, let us make sure
that the BSSID is non-zero.
Under what circumstances would the BSSID be zero?
//Peter
unassociated state for station.
but I observed this when i tested ad-hoc mode. I just started an ad-hoc
mode creator and left it for some time with no one joining. i observed
there are few frames in rx_tasklet of ath9k driver which seem to be
beacons and their BSSID is '0', as our curbssid is also '0' they seem to
be wrongly identified as 'my_beacons'. let me also verify it in STA mode
and find the effect of this before sending it as a PATCH.
let me also check if it has any effect in ath9k_process_rssi and ath_rx_ps.
--
thanks,
shafi
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
