Change TTL of mDNS/SSDP packets (Wiim Android/Plexamp)

Started by h3zwe, November 19, 2026, 09:27:27 PM

Previous topic - Next topic
November 19, 2026, 09:27:27 PM Last Edit: November 19, 2026, 09:52:09 PM by h3zwe Reason: typo
(I found https://forum.opnsense.org/index.php?topic=15405.0 but did not want to necro that thread)

As per https://forum.wiimhome.com/threads/issue-with-playing-plex-tracks-on-wiim-ultra.8132/, Plex and the WiiM Android app interact for service discovery over link-local multicast (SSDP/port1900, mDNS/port5353) on the same LAN subnetwork. This interaction has a time-to-live value in the multicast packet header of 1, so when it tries to cross the Docker bridge to another subnet, it gets dropped since the TTL is decremented by 1 and TTL=0 on the next subnet which is a drop rule.

Is there any way to fix this in OPNsense? I tried to set up 'UDP Broadcast Relay' similar to how I have it fix my 3D printer connection, but couldn't get it to work. It keeps stalling out at the internal Docker IP of my Plex server, without moving on to the actual advertised domain.

Quote from: h3zwe on November 19, 2026, 09:27:27 PMThis interaction has a time-to-live value in the multicast packet header of 1, so when it tries to cross the Docker bridge to another subnet, it gets dropped since the TTL is decremented by 1 and TTL=0 on the next subnet which is a drop rule.

Is there any way to fix this in OPNsense?
I don't expect, that the packets even reach the OPNsense interface. So there is nothing, OPNsense can do to forward them.
As you wrote yourself, it gets dropped in the docker bridge, since it is a gateway to your local network in fact.

Consider to connect the container to another virtual network, which has a layer 2 connection to OPNsense (and use UDP Broadcast relay to forward it to the other network segment).
Maybe this works with an macvlan in docker, I don't know.