Skip to content
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

MSEARCH response #18

Open
pawelewans opened this issue Jan 16, 2017 · 0 comments
Open

MSEARCH response #18

pawelewans opened this issue Jan 16, 2017 · 0 comments

Comments

@pawelewans
Copy link

pawelewans commented Jan 16, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant