DLNA listens on WAN interface

[daumas]

I have Jellyfin running on a server with two NICs. One is WAN (Internet) and the other is LAN. The server is also IP forwarding from WAN to LAN. Jellyfin is behind Apache and all clients (except DLNA) work both internally and externally.

Jellyfin used to listen on my LAN interface for multicast and SSDP traffic was working well. Clients could see and play without any hiccups. It seemed around the 10.9 era my clients were not working as well and I just never bothered to look into it. I've narrowed it down to why DLNA clients are no longer working as well as they used to.

I am seeing Jellyfin 10.10 listening on my WAN interface. My LAN DLNA clients don't get SSDP responses, but if they wait long enough they do get alive blasts and they can then see Jellyfin.

Looking at the DLNA plugin code it looks like it /should/ create a multicast broadcaster on all valid interfaces, but it isn't.

My networking page has the "Bind to local network address" box blank. I have LAN networks filled in with both the IPv4 and IPv6 LAN networks.

Am I doing something wrong? I wanted to create this thread before I started adding debug statements and re-compiling and/or creating a GitHub issue.

[TheDreadPirate]

What OS is Jellyfin running on and what installation method are you using?

[daumas]

Fedora 41 and bare metal. No container.

[TheDreadPirate]

Can you share your full jellyfin log via privatebin.net?

[daumas]

Sorry for not getting back. Real life calls.

I see there has been some movement on the code around network interfaces in 10.10.6 but it has not changed the multicast listen behavior.

10.10.6 log:
https://privatebin.net/?1c64694cf9924153...uLtanbtMdX

IPv4 and IPv6 addresses have been redacted but replaced with WAN/LAN identifiers.

[TheDreadPirate]

DLNA broadcasts would not go beyond the first couple hops. 4 is the default TTL. I wouldn't be surprised if your ISP's gateway would drop those broadcasts.

As for any concerns about DLNA listening on the WAN interface, you setup is atypical so I'm not entirely sure how that would behave.

If this were my setup, and I still needed Jellyfin accessible on the Internet, I would bind Jellyfin to the LAN IP and have my reverse proxy handle all external connections. This would mitigate issues with DLNA on the WAN port and still allow Jellyfin to be accessible without a VPN.