Proper state-handling

[ellie-idb]

A major issue I keep finding is: how do we handle 802.11 well? Taking examples from other 802.11 stacks, there's a transport layer and a hardware abstraction layer, as well as a higher level 802.11 layer.

Should we model our driver after these? How should we do such?

[zxystd]

According to 0f2a427 commit, means that use openbsd net80211 to handle AUTH->ASSOCIATE->RUN state? But this net80211 is limit as 11n phy mode, 11ac is not fully support.

[ellie-idb]

@zxystd Well, Apple80211 is limited in that it only does channel steering, EAPOL (WPA/WEP) authentication, and IE parsing. We have to do all of the rate selection, handle all of the management packets, and such internally, but I’m reconsidering reverting that commit and just building in the functionality internally through C++ because a lot of the functionality that ieee80211 has been replaced with code we wrote.

[mehmetyukcell]

Can I rebuild and try the kext?