Could you please enable DNS_DEBUG and TCP_DEBUG in lwip to check. Or could you please capture the air packet to see the DNS flow and TCP flow.

Hi mbratch It seems the socket has run out. Some of the sockets enter TIME-WAIT state and can't be released immediately. You can enable enable_so_linger option in https://github.com/espressif/esp-idf/blob/v5.0/components/esp_http_server/include/esp_http_server.h#L190. It will release the sockets im...

Hi mbratch It seems the socket has run out. Some of the sockets enter TIME-WAIT state and can't be released immediately. You can enable enable_so_linger option in https://github.com/espressif/esp-idf/blob/v5.0/components/esp_http_server/include/esp_http_server.h#L190. It will release the sockets imm...

Errno 113 generally is due to TCP SYN we sent with no response. You can use PC to connect WIFI-B and check whther TCP connection can be success.

Any update for your test?

你在哪个目录执行的？执行 git submodule update --init --recursive 有没有报错？另外你看下 rmaker_common 目录下有没有文件？

你需要执行下 git submodule update --init --recursive

Yes, As I explained above, this is not a problem. You can ignore it for esp_mqtt_handle_transport_read_error print.

D (00:03:25.783) mqtt_client: esp_mqtt_handle_transport_read_error: transport_read(): call timed out before data was ready! For question one, i think it is not a problem. We want to read data and no data received. This is only a debug log level.You can ignore it. assert failed: xQueueGenericSend qu...

Could you please capture the packet on your websocket server. It seems the server not response Sec-WebSocket-Accept in header. You can also capture the packet with your python websocket client. I can compare with them.