Serviio

I have a very unconventional network setup and serviio doesn't much seem to like it. It constantly complains about


Which isn't that surprising to me, thing is, it never gives up on this goal of acquiring a multicast socket and I don't actually need the DLNA or multicast functionality at all, I use it entirely for the web interface and web streaming, is there some way to just disable the DLNA functionality?

Without DLNA functionality, what possible use is Serviio for you? Besides, you have to have an IP address of some sort for your web access to function on any computer other than the one Serviio is installed on. Can't you select the proper network connection on the Serviio control panel at the bottom of the Status tab? How can you possibly make it work without an IP address (v4 or v6)? I know a fair amount about networking, and I'd be curious to hear more about your 'unconventional' configuration.

Wahhh, I forgot about this post. I only use the web interface, not DLNA. My network is pure IPv6 and pure layer 3, everything is routed (and I don't do PIM), so devices can't discover a DLNA server. My suspicion is that serviio really doesn't like the fact that it's IPv6 only? Although then that begs the question why is it picking IPv6 loopback? I'm honestly not sure what the problem is but given it's complaining about DLNA/multicast and I don't use DLNA I figured the easiest fix is disabling it. I'm not sure what serviio's rules are for interface selection or why it's picking loopback. The device doesn't have any other link/ether to pick from so maybe that's it? Ultimately serviio acts really squirrely, and I think it's because it's constantly stuck trying to find an IP for DLNA but can't, at least that's what the logs lead me to believe which is why disabling it would be my first step if that's even possible.

EDIT: I didn't address your question about the interface in the admin page, the only option in that menu is "Automatically detected" no other choices are listed.

I see your point, but that is a rather unique use case. Off the top of my head, how about adding a dummy network adapter that you can assign an IP address that doesn't work on your network and bind Serviio to that adapter? Yes, Serviio would be attempting to send out the multicast announcements, but they would only go to a dead connection. Nothing would appear on your real network and Serviio would be invisible to any connected device. As far as I know, the MediaBrowser web service does not bind to the Serviio assigned network adapter. This is just a guess on my part, as it's not something I've ever tried doing. But I have had Serviio on a computer with more than one network adapter, and I could bind Serviio to either one.