I used to see the event SYSTEM_EVENT_AP_STADISCONNECTED if the password was incorrect. Since updating to v3.3-beta1-268-g5c88c5996-dirty I see the following instead, but no events my application can handle. It is a bit like the scan not possible situation where you get output on the serial monitor but no event. Is this a planned architectural change or feature?
I (25728) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (25729) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bgn, 40U
I (29731) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 134242
I (29731) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (29776) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (29776) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bgn, 40U
I (33778) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 134242
I (33778) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (33819) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (33820) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bgn, 40U
I (37821) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 134242
I (37822) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (37863) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (37863) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bgn, 40U
I (41865) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 134242
I (41865) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (41907) wifi: new:<1,1>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (41908) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bgn, 40U
I (45909) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 134242
I (45909) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<255,255>, prof:1
I (46531) wifi: new:<1,0>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
I (46532) wifi: station: 70:c9:4e:d3:b6:17 join, AID=1, bg, 20
I (50029) wifi: station: 70:c9:4e:d3:b6:17 leave, AID = 1, bss_flags is 131106
I (50029) wifi: new:<1,0>, old:<1,0>, ap:<1,1>, sta:<255,255>, prof:1
Incorrect WiFi password no longer triggers SYSTEM_EVENT_AP_STADISCONNECTED on esp-idf v3.3-beta1-268-g5c88c5996-dirty
Re: Incorrect WiFi password no longer triggers SYSTEM_EVENT_AP_STADISCONNECTED on esp-idf v3.3-beta1-268-g5c88c5996-dirt
According to my observations in the new versions of IDF (it seems after 3.0.x) all password login modes on the WIFI_AUTH_WPA_WPA2_PSK access point do not work
however, logging in without a WIFI_AUTH_OPEN without password works fine.
I do my code in the process of creating use WIFI_AUTH_OPEN
I also noticed that apple devices successfully connect via WIFI_AUTH_WPA_WPA2_PSK, while android does not work
however, logging in without a WIFI_AUTH_OPEN without password works fine.
I do my code in the process of creating use WIFI_AUTH_OPEN
I also noticed that apple devices successfully connect via WIFI_AUTH_WPA_WPA2_PSK, while android does not work
I (27201) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (27203) wifi: station: 30:a8:db:cf:5a:62 join, AID=1, bgn, 20
I (63361) wifi: station: 30:a8:db:cf:5a:62 leave, AID = 1
I (63363) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (67905) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (67907) wifi: station: 30:a8:db:cf:5a:62 join, AID=1, bgn, 20
I (104057) wifi: station: 30:a8:db:cf:5a:62 leave, AID = 1
I (104059) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (108659) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (108661) wifi: station: 30:a8:db:cf:5a:62 join, AID=1, bgn, 20
I (144807) wifi: station: 30:a8:db:cf:5a:62 leave, AID = 1
I (144807) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (149367) wifi: n:11 2, o:11 2, ap:11 2, sta:11 2, prof:11
I (149369) wifi: station: 30:a8:db:cf:5a:62 join, AID=1, bgn, 20
Re: Incorrect WiFi password no longer triggers SYSTEM_EVENT_AP_STADISCONNECTED on esp-idf v3.3-beta1-268-g5c88c5996-dirt
I'm using WIFI_AUTH_WPA2_PSK which does work with Android and as I understand it is more secure than mixed mode WPA/WPA2 and seems ubiquitous on devices now. The new problem is detecting when the user has entered an incorrect password.
Who is online
Users browsing this forum: Baidu [Spider] and 179 guests