-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
Once the app sends a mSearch, it waits for clients to respond, even after getting a response, it doesn't trigger the read socket function. It waits forever but receives no data to the app layer.
Select(lssdp->sock, &fd, &ts) doesn't return a value greater than 0 ever for unicast messages
Wireshark traces shows app receiving client response after an mSearch multicast message and soon after the app received the HTTP ok from client it issues a UDP packet back to the client to the same socket it issued the mSearch from and reports a failure (that's obvious client won't have that socket open anymore)
Also, it update the neighbors_list only via notify messages
Any help would be much appreciated
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
