[net80211] add initial support for HT upgrade of IBSS nodes. * add ability for IBSS nodes to be upgraded when it sees HT IEs * add HT IEs to probe requests/responses and beacons * send a probe request after bringing up a node so we can...

[adrian]

Summary

...potentially

upgrade it to 11n if we see a probe response with HE IEs.

The 802.11 spec notes that a subset of HTINFO is allowed for IBSS, so
ensure we add it. However, there's nothing in the spec that fully
explains how nodes negotiate IBSS. Eg, we may want to not start sending
traffic until a probe request/response occurs so we don't have to
re-init the node with updated rate control information.

[avos]

sys/net80211/ieee80211_output.c

2077

As I can see, this variable is never used here. Is something missing?

[adrian]

ping? any comments?

[avos]

sys/net80211/ieee80211_output.c

2085

Still have no idea why it is referenced here

[adrian]

sys/net80211/ieee80211_output.c

2085

Because vap->iv_bss can be changed/recycled at any time, and unless you're holding the node table lock, you're not guaranteed to get the stable version.

Now, this is also not guaranteed to get the stable version because of how the node reference counting is implemented - it's an atomic, and it's quite possible that something is freeing the node whilst you're busy getting a reference on it - but this reduces the window way way down and it's the "right" way to be getting access to iv_bss anyway.

[avos]

sys/net80211/ieee80211_output.c

2085

There are no users of it (yet?)

[adrian]

sys/net80211/ieee80211_output.c

2085

Look at the drivers. :)

[avos]

sys/net80211/ieee80211_output.c

2085

It's not used during Tx (ieee80211_raw_output() -> ic_raw_xmit()) (ath, mwl, iwn, ...)