I have next network infrastructure:
- Gateway server (ubuntu 12.04.5 x86 + hostapd ath9k based AP 300mbit)
- 1 wired client
- 5 wireless clients
All connected wireless clients are in 802.11n mode and work stable (connectivity is robust and stable).
Now i'm trying to connect ESP8266 to my AP.
The first problem I have faced is that I just can't connect ESP to my AP because of failed association and then authentication (log from hostapd):
Code: Select all
IEEE 802.11: did not acknowledge association response
IEEE 802.11: did not acknowledge authentication response
The problem here is that STA unable to ack several frames, but the hostapd needs them to be acked. As a workaround I have patched hostapd to ignore those frames. ESP now able to connect to my network.
Next problem that I have faced is that ESP8266 became unaccessible from other machines in my network after about of 10 seconds. My investigation resulted in that the ESP get removed from the ARP cache of machine from which you try to access it. This leads to next situation: after ESP connect to AP and got IP it can be accessible from any machine on the network for about of 10 seconds. If you not access ESP in that period it became inaccessible. I have found 2 workarounds for this:
1) assign static IP to ESP and infinitelly ping it
2) assign static IP to ESP and add static ARP record
The question: is there any straight solution to solve those two issues?
It's impossible to use ESP in any wireless projects with those "baby diseases".