| commit | 356cb55d81d1692bd74b96c71deeb7e1cf956196 | [log] [tgz] |
|---|---|---|
| author | Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> | Wed Dec 07 16:51:38 2011 +0530 |
| committer | John W. Linville <linville@tuxdriver.com> | Fri Dec 16 09:27:56 2011 -0500 |
| tree | 49a38e815bd2caf80eec8ef5d6ab73696c0fa712 | |
| parent | d66be8294289346ceba4c6abc022954b682d4959 [diff] |
ath9k: validate for non-zero BSSID before concluding that the recieved beacon is for us, let us make sure that the BSSID is non-zero. when I configured ad-hoc mode as creator and left it for some time without joining I found we recieved few frames whose BSSID is zero, which we concluded wrongly as 'my_beacons' Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>