Cannot connect ESP8266 MQTT devices #170
Comments
|
The client can't connect to AP? What is the client chip? |
|
ESP8266. I have 11 of them in my home that will not connect to my wifi with the DD-WRT with latest driver. I have confirmed now that an Archer C7v2 with latest DD-WRT will connect them and a DIR-860L router with LEDE installed will connect them. It is only the DD-WRT with that latest mwlwifi driver installed that cannot connect the IoT devices . |
|
Can you give me more information about your problem? |
|
Please let me know version of your mwlwifi and firmware. Setting of your AP. If possible, please use "logread | grep hostapd" and "dmesg" to get more information for me. |
|
dmesg `[ 0.000000] Booting Linux on physical CPU 0x0 ` logread
mwlwifi
|
|
|
|
Please help to check if this problem will happen if only one client is used to connect to AP. Thanks. |
|
The AP's both 2.4 and 5Ghz will connect to clients, just not the ESP8266's. I changed the wifi name and reprogrammed one ESP8266 and it still wouldn't connect. Subsequently then changed the wifi connection for a raspberry pi and it connected fine. |
|
What is ESP8266? |
|
ESP8266 is an Internet of Things chip found in a lot of Home Automation stuff. I have 6 wifi outlets, a motion sensor, 2 relays and an LED strip all controlled by ESP8266 chips. What they do is broadcast a hotspot which you connect to and then configure them to run on your local network. These devices all work brilliantly on any SSID named "dd-wrt" with the appropriate password. Works with my WRT1900ACS, Archer C7v2, DIR-860L, and R7800 routers. Those ESP8266 devices will not connect using the last two (and possibly previous) BrainSlayer DD-WRT versions using the mwlwifi version I posted above. Regular computers work just fine. I can connect my laptop, my raspberry pi's, anything but the ESP8266 devices. |
|
This will give you a rough idea of the device http://www.hagensieker.com/blog/page/?post_id=44&title=esp8266-hack-of-inexpensive-wifi-outlet |
|
The latest driver can work for WRT1900ACS and WRT3200ACM, you only encounter this problem with WRT3200ACM, right? |
|
BTW, do you have the same problem with stock firmware of WRT3200ACM? |
|
That is correct. Only on the 3200ACM The version of DD-WRT I'm running on the WRT1900ACS is dated 3/30 and I haven't run latest firmware yet. Have not tried stock yet but every other dd-wrt on every other device works fine. |
|
|
I'm booting to stock now will know in a few minutes. I haven't tried to test on open network as I'd have to reprogram the devices. I can later but not a ton of time before work this morning. Will test stock now. |
|
Thank you. These tests can help me to check this problem. If you can capture traffic between AP and ESP8266, it would be even better. |
|
Stock works. |
|
Can you help just connect one ESP8266 to AP to see if it works. Thanks. |
|
I'll try to wireshark but won't be able to get to it for a couple days. Quick work trip. |
|
|
One ESP8266 does not connect. I have wireshark but will have to capture later. Consequently yesterday I installed 17.01.1 LEDE and then updated the kmod-mwlwifi driver and it also did not work |
|
If you use LEDE, you can use "logread | grep hostapd" to get more debug information. |
|
Will give that a shot later. Out the door for work and probably won't be able to provide more info until Wed. Many thanks for your help here this morning. |
|
I think I've seen a post reporting problems with recent drivers that only
happened with an encrypted connection, an open connection worked (using the
esp8266)
|
|
Please use https://drive.google.com/open?id=0B3qLWtcWB9EdcHJvd2tIbHl3dnM to do test and use "logread | grep hostapd" to get more information. I will check the log and update needed debug package to check this problem. Thanks. |
|
Will do tomorrow when I get back off my trip. Thanks. |
|
Installed your LEDE and here is the logread:
|
|
|
@insaneFu Please don't disable WMM and get station information for me. |
|
@yuhhaurlin Interesting: now many devices do connect, maybe because there was still an active DHCP lease on the router? But on some devices, error accurs as known. (deauthenticated due to inactivity (timer DEAUTH/REMOVE)) When devices do not connect due to error, they don't make it into the file, so we can be glad I can give you this now: Amazon Fire Tablet: nodeMCU V2: sonoff remote switch: |
|
Which one is ESP8266? If it can't connect with security mode, please use open and give me capability of ESP8266. |
|
@yuhhaurlin nodeMCU V2 and sonoff remote are both esp8266. confirmed my theory that connection with N and WMM and active security was still possible because of active DHCP lease. Was not possible for any esp8266 device after router reboot. Here is data for one esp8266 (nodeMCU) on a fresh booted router with N / WMM active and no security: |
|
So the device is connected to WRT3200ACM with security! What the problem is? |
|
i see no relation to dhcp and connection problems. could it be that the esp device has a problem with broadcast packets in 802.11n mode, so that it cannot receive a dhcp lease? mmh maybe disable DHCP-Authoritative on your dhcp server which can be a cause for bad client implementations |
|
Please read again. Connection with N and WMM and active security is only possible if there is still an active DHCP lease. After next router reboot, devices will not connect (known error). Connection on a fresh booted router without active DHCP lease is only possible with eiter N/WMM or security turned off. |
|
It sounds like not a problem of mwlwifi. |
|
Maybe the problem is in hostapd, I read about that in another thread, but cannot find it right now. Plus, on any other router, things do also work out perfectly. I will try disabling DHCP authoritative later, have to go for now. Thanks so far. |
|
Setting the DHCP server to non-authoritative does not help. I know it seems not to be a mwlwifi problem, but then on the third non-mwlwifi radio of the WRT3200ACM, everything works fine, at least until the third radio itself being unstable crashes the whole connection (for every device, even non-esp8266). In the meatime, I found that mentioning of a bug in hostapd on OpenWRT I was looking for, but there is no reference to esp8266, so this is probably something completely different: On the other hand, there are indeed threads about esp8266 killing wifi networks: In the end, I have no clue where to continue my search, but with only G wifi and without WMM, everything at least works for now. Will be happy if someone has another idea, but for now, the matter is - if not resolved altogether - at least avoided for me. Again thanks to everyone for trying. |
|
@yuhhaurlin might this problem be fixed with the new firmware you released for testing? i mean it could be the same issue |
|
I think they can try to test the new firmware. But I have no idea if it fixes this problem here. |
|
I remember they reported that this device has no problem to connect with stock firmware. |
|
@BrainSlayer If there's a dd-wrt build with that in it I could test, in wrt3200acm. |
|
let me do one for you |
|
ftp://ftp.dd-wrt.com/others/test/linksys-wrt3200acm/ |
|
@BrainSlayer I Loaded that and have been testing it but I found it was selectively cutting my connection with some web sites like yahoo mail and Ookla speed test and some others, very strange behavior for something to selectively stop only certain IP addresses (as if it had hidden qos). |
|
only the mwlwifi firmware has been changed. there is no selective ip filter inside unless you defined one |
|
I understand there is no intentional filter, Something is wrong with it it will not allow access to certain web sites If I reload 34315 it works fine as well as the old stock linksys I've been falling back on. I've never seen it before so Yes I'll try Nvram erase as well, and post here if any different. |
|
@BrainSlayer I tried different computers with different Os's wired and wireless, the router is the only thing that can possibly be preventing some web access. |
|
unfortunatly that all wont answer the question if the ESP device is able to connect |
|
actually the aruduino with that chip (arduino + esp8266) will connect and stay connected for the hours about 7 with other ap's nearby I left it up it was fine, I guess I got side tracked, for that the connection seems to be like other devices now. so problem with 8266 connection seem,s gone. |
|
8266 getting dhcp no problem |
|
so even if esp devices work with this new firmware. i found out that this new firmware breaks everything for me with wds sta |
|
I will check it. Thanks a lot. |
|
is this issue supposed to be closed? esp8266 devices only work for me by disabling WMM and disabling N mode |
|
I can confirm this issue still exists with openwrt dev build as of 4/8/2018 |
|
I reached this thread after finding out I have a problem with ES8266 devices (SONOFF) and WMM. |
|
This problem has been spotted so many time ago, this should be fixed ASAP... Implementing features like MU-MIMO shouldn't be a higher priority than things that broke connectivity like this one... Yes MI-MIMO should be implemented, but if something broke connectivity, this should be fixed first... It's almost 2 years and this router still broken to a point a ESP8266 cannot connect to a router... This is becoming a joke... |
I have a Linksys WRT1900ACS with DD-WRT dated 3/30 which works perfectly and controls many IoT devices in my home.
I have a WRT3200ACM that I intended to deploy as my main router in the home. Using the latest Brain Slayer DD-WRT versions 31 May and 1 June. With this router, using the mwlwifi driver, and configuring the wifi identical to the previous router 10 of my devices, all of which use ESP8266 chips will not connect to the same network. I have tried turning off the SPI firewall, port forwarding to the MQTT server, changing the wifi name entirely and reconfiguring a device to that new name...........nothing allows these devices to connect.
Out of curiosity I took an Archer C7v2 and put latest DD-WRT on it and it will connect all my ESP8266 devices with no problem.
I posted about this issue on the DD-WRT forums and there is another person with similar problems on the forum using WRT3200ACM and Home Automation devices.
I suspect this is an issue with the mwlwifi driver possibly.
Thanks............John, New Bern, NC.
The text was updated successfully, but these errors were encountered: