-
-
Notifications
You must be signed in to change notification settings - Fork 212
GIGAR1: conflict between Access Point and common WiFi connection #858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A WiFiClient instance is bind with network after first connect, so it will still try to use AP if it was first used with AP. |
please try in SocketWrapper library in AClient.cpp in AClient:stop() add |
Dear Juraj,
|
my intuition says it is the server now. try to EDIT: repeated |
I supposed so. Indeed, I tried to do:
However, this seems to makes things even worse. |
Hello,
I am facing some issues while trying, in a larger project, to accomplish the following:
Every time I close a connection, I call
WiFi.disconnect()
andWiFi.end()
; Moreover, when AP operations are completed, I callWiFiClient::stop()
. MyWiFiClient
object is global and obtained throughWiFiServer::available()
.After closing AP connection, I could connect to the WiFi but any connection (e.g., to www.google.com) failed by a time-out. I kind of solved the problem through the following code I invoke every time I switch between point 1 and 2 of the algorithm.
WiFi = WiFiClass(WiFiInterface::get_default_instance());
However I do not understand such a behaviour.
Now, if WiFi connection fails after AP was accomplished once, AP is opened again, but this time
WiFiServer::available()
fails, in the sense that no data are ever available. However, I controlled network traffic through Wireshark and I see that DNS management throughWiFiUDP
succeded, while an http requestGET /wpad.dat HTTP/1.1
was sent by the client, but never received by the server.It seems to me that there are library issues then, or at least poor documentation for me to be able to understand whether I am doing anything wrong
The text was updated successfully, but these errors were encountered: