You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Board: ESP32_Core_board_V2
Core Installation/update date: 10/apr/2018
IDE name: Arduino IDE
Flash Frequency: 80Mhz
Upload Speed: 115200
Description:
A Wi-Fi network is set up with two access points using the same SSID; each access point is configured to use a different subnet (10.38.0.0/255.255.255.0 for the first access point, with IP address 10.38.0.1, 10.38.1.0/255.255.255.0 for the second access point, with IP address 10.38.1.1). Each access point runs a TCP server listening at port 5555.
ESP32 is configured to connect to one of the 2 access points by specifying the corresponding BSSID, and is set up with a static IP address. After a Wi-Fi connection, ESP32 connects to the TCP server running in the current access point. A procedure is also in place to make ESP32 switch from one access point to the other (reconfiguring the static IP address so that it belongs to the same subnet as the access point being connected to).
The problem is that upon switching access point, most of the times ESP32 is unable to connect to the TCP server (the errno value set by lwip_connect_r() is 113, which means "no route to host").
Sometimes it works, but most of the times the TCP connection attempt fails with the above errno (the Wi-Fi connection is always successful); and when it fails, any subsequent attempts to connect fail as well.
The sketch below, which reproduces the problem, switches from one access point to the other when something is received on the serial port.
I also noticed that if I reset the board (with the hardware reset button) when the ESP32 is configured to connect to access point #0, at the next reboot most of the times it is unable to connect to the TCP server of access point #1 (which is the first access point chosen by ESP32 after a reset); if I reset again, it can successfully connect; so it seems the last configuration before the reset affects the ability of the ESP32 to connect after the reset.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
Hardware:
Board: ESP32_Core_board_V2
Core Installation/update date: 10/apr/2018
IDE name: Arduino IDE
Flash Frequency: 80Mhz
Upload Speed: 115200
Description:
A Wi-Fi network is set up with two access points using the same SSID; each access point is configured to use a different subnet (10.38.0.0/255.255.255.0 for the first access point, with IP address 10.38.0.1, 10.38.1.0/255.255.255.0 for the second access point, with IP address 10.38.1.1). Each access point runs a TCP server listening at port 5555.
ESP32 is configured to connect to one of the 2 access points by specifying the corresponding BSSID, and is set up with a static IP address. After a Wi-Fi connection, ESP32 connects to the TCP server running in the current access point. A procedure is also in place to make ESP32 switch from one access point to the other (reconfiguring the static IP address so that it belongs to the same subnet as the access point being connected to).
The problem is that upon switching access point, most of the times ESP32 is unable to connect to the TCP server (the errno value set by lwip_connect_r() is 113, which means "no route to host").
Sometimes it works, but most of the times the TCP connection attempt fails with the above errno (the Wi-Fi connection is always successful); and when it fails, any subsequent attempts to connect fail as well.
The sketch below, which reproduces the problem, switches from one access point to the other when something is received on the serial port.
I also noticed that if I reset the board (with the hardware reset button) when the ESP32 is configured to connect to access point #0, at the next reboot most of the times it is unable to connect to the TCP server of access point #1 (which is the first access point chosen by ESP32 after a reset); if I reset again, it can successfully connect; so it seems the last configuration before the reset affects the ability of the ESP32 to connect after the reset.
Sketch:
The text was updated successfully, but these errors were encountered: