-
Notifications
You must be signed in to change notification settings - Fork 13.3k
esp8266, openwrt can't connect #9234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Duplicate of #7965 (and some other ones) You got the main gist of forcing G mode, iirc it is the main reason
Please update to Core 3.1.2 |
initially I tried the latest version of SDK. then I found somewhere that after 2.5 many people stopped connecting, so I switched to it.
wifi AP log
|
Not much to go on, really. You can't use WPA3, in case you are forcing it. Only WPA2 2.4GHZ works. Just to clarify some terminology
NONOS SDK is a closed-source blob from Espressif, WiFi and low level networking is handled there. Why I mentioned this - 2.4.2 -> 2.5.0 switch switched from SDK:2.2.1 to SDK:3.0.0-dev by default. 2.6.0+ switched back, 2.7.0+ ship with SDK:2.2.2(from various git dates). If you had it working before 2.5.0, swap to SDK:2.2.1 and try again (or any other available version) |
I used nodemcu and nexx wt1520 openwrt 15 before... . Now I changed the hardware to x86 openwrt OpenWrt 23.05. 5 hardware AP
cat /etc/config/wireless
flash sketch with full erase. |
No mfp support for NONOS, ieee80211w 'required' likely the cause |
i try WPA-PSK/WPA2-PSK Mixed and TKIP CCMP without success. this #7965 (comment) ? or some else? i use Wemos D1 mini r2 & mini board profile the device appears in the web interface for a few seconds. Tr 0, but this behavior occurs even at 30 cm from the router. |
check old AP settings
and to old AP modele connect fine
try Wemos D1 mini r2 & mini board profile |
fixed
set AP option ieee80211w '1' and all work |
trying to connect esp8266 to access point. simple sketch.
router log only one entry
...
daemon.info hostapd: wlan1: STA yy:yy:yy:yy:yy:yy IEEE 802.11: authenticated
daemon.info hostapd: wlan1: STA yy:yy:yy:yy:yy:yy IEEE 802.11: authenticated
daemon.info hostapd: wlan1: STA yy:yy:yy:yy:yy:yy IEEE 802.11: authenticated
...
esp does not receive ip address.
i don't know if this is an esp or AP problem
The text was updated successfully, but these errors were encountered: