| commit | 8ec51a39812ec931f77655905868541024dd6585 | |
| author | Sepherosa Ziehau <sephe@dragonflybsd.org> | |
| Wed, 29 Nov 2006 15:12:10 +0000 (29 15:12 +0000) | ||
| committer | Sepherosa Ziehau <sephe@dragonflybsd.org> | |
| Wed, 29 Nov 2006 15:12:10 +0000 (29 15:12 +0000) | ||
| tree | 155c2e709648f04ec32ea85283a2455045acbf83 | treesnapshot (tar.gz zip) |
| parent | e3e0efe4b3780f9f107c8428fa8d202e4ceace05 | commitdiff |
Don't use unprocessed (e.g. negociated) peer node's rate set to fill
Supported rates ie of Association Request, instead, use own supported
rate set (i.e. ieee80211com.ic_sup_rates).
In the orginal way, following senario is broken:
- STA is 11b
- AP is 11g
STA will send out sorted AP's rate set in Association Request. Obviously
STA will not be able to receive at any data rates > 11Mbit/s. So this
breaks IEEE Std 802.11b subclause 10.3.3.1.2:
"... The STA must be able to receive at each of the data rates listed
in the set. ...".
Supported rates ie of Association Request, instead, use own supported
rate set (i.e. ieee80211com.ic_sup_rates).
In the orginal way, following senario is broken:
- STA is 11b
- AP is 11g
STA will send out sorted AP's rate set in Association Request. Obviously
STA will not be able to receive at any data rates > 11Mbit/s. So this
breaks IEEE Std 802.11b subclause 10.3.3.1.2:
"... The STA must be able to receive at each of the data rates listed
in the set. ...".
| sys/netproto/802_11/wlan/ieee80211_output.c | diffblobblamehistory |