04-09-2025, 05:43 PM
On accessing your player via symbolic <hostname>..local mDNS address versus numeric IP address,
This may be unrelated to the problem(s) expressed in this thread, but I had problems with my player (assume it's named moode) coming up variously as moode.local, moode-2.local, etc.[1]
This turns out to be a known problem with Linux and the mDNS resolver avahi. Apparently there is a possible race condition with multiple interfaces such as with both IPv4 and IPv6 interfaces enabled in moOde (I have both IPv4 and IPv6 service through to the Internet). I pointed out what I had learned in my Google searches to Tim and he recently modified moOde as a result.
If you go to m > Config > System and scroll down to the Networking section, you'll see the new-ish mDNS discovery setting. By default, it's set to "IPv4 and IPv6 (default)" but it can be changed to "IPv4 -only".
Changing this setting on all my players has seemingly fixed my particular problem. I'm curious if it is of any help for the users posting to this thread.
Note - just yesterday, I came across a post elsewhere which suggests that librespot's discovery code may be another contributor to the problem. In my case, only the change Tim's already made was necessary but YMMV.
Regards,
Kent
[1] As it happens, I have no local DNS resolver running on my LAN so mDNS is all that matters to me.
This may be unrelated to the problem(s) expressed in this thread, but I had problems with my player (assume it's named moode) coming up variously as moode.local, moode-2.local, etc.[1]
This turns out to be a known problem with Linux and the mDNS resolver avahi. Apparently there is a possible race condition with multiple interfaces such as with both IPv4 and IPv6 interfaces enabled in moOde (I have both IPv4 and IPv6 service through to the Internet). I pointed out what I had learned in my Google searches to Tim and he recently modified moOde as a result.
If you go to m > Config > System and scroll down to the Networking section, you'll see the new-ish mDNS discovery setting. By default, it's set to "IPv4 and IPv6 (default)" but it can be changed to "IPv4 -only".
Changing this setting on all my players has seemingly fixed my particular problem. I'm curious if it is of any help for the users posting to this thread.
Note - just yesterday, I came across a post elsewhere which suggests that librespot's discovery code may be another contributor to the problem. In my case, only the change Tim's already made was necessary but YMMV.
Regards,
Kent
[1] As it happens, I have no local DNS resolver running on my LAN so mDNS is all that matters to me.
