【Feedback】Socke Accept takes 30 seconds on RTOS SDK 1.4.0

[cloudmonitor24]

We created an application quite simple using RTOS SDK version 1.4.0:

- Wifi is configuread as an AP
- Static IP assigned (192.168.1.1)
- DHCP Server enabled

Then we made a very simple socket listening on port 80, using the standard socket programming functions: lwip_socket, lwip_bind, lwip_listen and lwip_accept on a thread created at boot.

Any client can successfully join the WiFi network and get an IP address from DHCP server (typically 192.168.1.2, the first available) but once we try to connect to socket listening on 192.168.1.1:80, it takes about 30 seconds to connect.

We don't think it's a matter of CPU performance because any other operation (join/leave wifi network, ping or whatever) is very quick. Only connecting to that listening port is so slow.

I don't think it's a matter of SDK 1.4.0 because we didn't try the same application on previous versions.

[ESP_Faye]

Hi,

The time it costed for connection depends on the network environment. If the network environment is good, it will take less time to create a connection.

You can try to ping the IP address. Or use Wireshark to capture the WiFi Packets for analysis.