lars18th
commented
3 years ago Hi @sonic42 ,
Yes, the announcement of the SSDP is quite complex to manage inside a multihomed server. In fact, the SSDP could be understanded is an independent process of the RTSP service. The fact is that the developers of the SAT>IP standard never have considered a multihomed server. And this have some consequencies: for example, the SSDP announcement can bind only to one network addresss. The reason is because in the RTSP protocol the server needs to publish his address and the client requires to know and use it. So if the client connects with the server using a secondary address then the server needs to manage this. Quite complex in fact! So the standard doesn't support this.
Nevertheless, some workarounds exist. My prefered solution is this: run minisatip only in one network address. And if you need to leave the option to connect using other addresses, then run a proxy on each of these addresses that connects to the main minisatip. The proxy could be another minisatip instance or a pure SAT>IP proxy. In any case, the SSDP announcement requires to be done one-per-address. So if you're running a proxy in the same machine then take note that SSDP is multicast. And then you need to restrict the addresses where you publish it. And as this it's a pain, I prefer to run the proxies in other machines (or inside a container). Then you can isolate the multicast SSDP announcement.
I hope this helps you. Regards.
sonic42
This is a feature request. On systems with more then one network interface it's possible to select one or more specific network interfaces. With my tests, the daemon binding on all interfaces with port 554 but the service SSDP announcement is only on first interface.