Help needed for local server discovery (UDP Broadcast response) - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Development (https://forum.jellyfin.org/f-development) +--- Forum: Client Development (https://forum.jellyfin.org/f-client-development) +--- Thread: Help needed for local server discovery (UDP Broadcast response) (/t-help-needed-for-local-server-discovery-udp-broadcast-response) |
Help needed for local server discovery (UDP Broadcast response) - GeoffreyCoulaud - 2023-10-02 Hello! I've been working for a few days on a Python/GTK/LibAdwaita client for Jellyfin, for fun mainly. Here is the repo if anyone is curious (very early stage) I need a little bit of help with local server discovery. The general networking docs specify that servers can be discovered by broadcasting "Who is JellyfinServer?" on 7359 UDP. This does work, by analyzing the network with wireshark I can see the expected response. However, I can't get a response message in python with the socket opened to broadcast. But if I hardcode the local Jellyfin server address instead of the interface multicast address, then I can get a response fine. I've read online that multicast could be more appropriate here, but I don't understand which parameters to use for it. (which multicast group, and why?) Can anyone give me a little bit of advice here? (UPDATE) I've attached a Wireshark capture of UDP on the Jellyfin server IP. On it, we can see that the response does arrive to my machine. The destination port changes everytime tho, that is intriguing. Extract of the Python code (github permalink) : Code: def detect_servers_thread_func(self) -> None: RE: Help needed for local server discovery (UDP Broadcast response) - GeoffreyCoulaud - 2023-10-03 Update: I tried spinning up a test Jellyfin server with docker on my local machine, and it does get picked up. This makes me think that it may be a network configuration issue? I'd love a hint to what could be misconfigured. |