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
Hi Satoshi,
I am using your library for the ssdp component.
On startup the ssdp notify messages are being sent to port 1900.
However, when an msearch is sent from various browsers/routers, I can see the msearch on wireshark going out on port 1900. However the response is not recognised by wireshark as an SDP packet but it is a directed response to the IP address and port of the device doing the msearch. I notice the source port of the response is not 1900 but a dynamically allocated port number.
Also, the device is never listed in the browser.
Maybe the source port of the response should be 1900 but I cannot find in the code where to change this. I've tried fixing it in the socket functions but it always uses a dynamic one.
If you have any advice or suggestions would be most appreciated.
Paul
The text was updated successfully, but these errors were encountered:
Hi Satoshi,
I am using your library for the ssdp component.
On startup the ssdp notify messages are being sent to port 1900.
However, when an msearch is sent from various browsers/routers, I can see the msearch on wireshark going out on port 1900. However the response is not recognised by wireshark as an SDP packet but it is a directed response to the IP address and port of the device doing the msearch. I notice the source port of the response is not 1900 but a dynamically allocated port number.
Also, the device is never listed in the browser.
Maybe the source port of the response should be 1900 but I cannot find in the code where to change this. I've tried fixing it in the socket functions but it always uses a dynamic one.
If you have any advice or suggestions would be most appreciated.
Paul
The text was updated successfully, but these errors were encountered: