Closed igorkulman closed 4 years ago
More information: I noticed after reading the state of the WiFi card while trying to authenticate the SSID, regardless if the password is right or wrong, the status when it's trying to connect actually returns ITL80211_S_SCAN
rather than ITL80211_S_ASSOC
or ITL80211_S_AUTH
.
Another issue, even connecting to an SSID and PURPOSEFULLY entering the wrong password, the status returns ITL80211_S_RUN
even if it's the only SSID that has been attempted to associate. During the authentication/associating the status returns ITL80211_S_SCAN
.
Expectations: If the WiFi failed to connect, it should go back to ITL80211_S_INIT
and when it tries to connect, it should return ITL80211_S_AUTH
or ITL80211_S_ASSOC
.Assuming there was no previous associations with other ssid.
Edit: This HeliPort branch just improves detecting power state and shows "correct" state of the WiFi card, and fetching status always runs in the background if the WiFi card is on.
Uploaded video so you can see what I mean. The password of the SSID is not a correct password but the state on the itlwm states that it still connects even if it fails authentication.
can you check the latest code? thank you.
On Intel 7260 AC when I just load the kext with my networks in Info.plist it always works fine.
With HelkiPort when I connected to a different network only most only works on second try, never on first try. Sometime I get to a state when I cannot connect back to my original network.
In my example, logs attached, I connected to K-guest and then was trying to connect back to K.
Although the status was connected I either got not IP address
Or a self assigned IP address
I tried renewing DHCP lease in System Preferences but it did not help.
I had to unload the kext and load it again to make it work again with K.
Logs: itlwm.log