UDP 1900

[linuxserver]

UDP 1900

[hoppel118]

Hi guys,

I saw your comment about using a macvlan. This didn't work for me. My complete story I described here: netdata/netdata#6527

Regards Hoppel

[tobbenb]

I don't think there is much to do with this issue other than giving tvheadend its own IP using macavlan.

[nomandera]

At the very least we need to document and explain the situation. Currently we have no info at all that suggests users have cater for UDP port clashes on a multicast host address for SSDP.

I imagine most wont even know what these words mean.

[tobbenb]

I don't think we should be the ones to document every issue that might occur when using the containers. Then the Readme would be bloated.
Wouldn't this still happen if you run both emby and tvheadend on the same host also?

[nomandera]

Yes it would. At the very least we should publish the ports a container uses and why or you end up with users giving wrong advice to bridge UDP 1900 (as can be seen #92)

[nomandera]

Proposed updated wording

If you use IPTV, SAT>IP or HDHomeRun, you need to create the container with --net=host and remove the -p flags.

This is because to work with these services Tvheadend requires a multicast address of 239.255.255.250 and a UDP port of 1900 which at this time is not possible with docker bridge mode.

If you have other services which also use multicast such as SSDP/DLNA/Emby you may experience stabilty problems. These can be solved by giving tvheadend its own IP using macavlan.