Hi,
My mdns server and websocket server were working properly for a long time.
I ended up putting the project aside for few months because i am waiting for the launch of the esp32-s3 modules.
When i came back to the project i decided to do some tests, and the mdns server was behaving strangely.
Using wireshark i saw that the mdns server sent the ad for about 6 times and stopped(after manual reset).
The first 4 times every 1 seconds and the last 2 times every 2 seconds and stopped.
I configured mdns on menuconfig so that it would send the notification to the network every 1 second.
During this period we moved to an new internet provider and also to a new wifi router.
I thought the problem could be the new wifi router, but i haven't been able to find the problem yet.
So i decided to update the esp-idf.
I updated to v4.4-dev-1254-g639e7ad49.
After esp-idf update the mdns problem still persists.
And now the websocket server also bugged.
Using the idf.py monitor, i can see that websocket server start ok, but when i connect to the server through my android application, the following message appears:
W (00:00:08.807) httpd_ws: httpd_ws_get_frame_type: Failed to read header byte (socket FD invalid), closing socket now
W (00:00:08.816) httpd_ws: httpd_ws_get_frame_type: Failed to read header byte (socket FD invalid), closing socket now
Before the update of the esp idf, the websocket server worked ok, including "ESP-IDF Release v4.2.1".
Some suggestion on how to resolve the mdns server and now the websocket server bug ?
Note: i changed the httpd priority from "config.httpd.task_priority = tskIDLE_PRIORITY + 5" to "config.httpd.task_priority = configMAX_PRIORITIES".
@david-cermak
Thank's.
Issues with mdns server and now with websocket server too
Re: Issues with mdns server and now with websocket server too
Hi,
I installed esp-idf version v4.2.1 and websocket server it's OK now.
I installed esp-idf version v4.2.1 and websocket server it's OK now.
Who is online
Users browsing this forum: Bing [Bot], Ethapus and 259 guests