[SOLVED] Moode 9.0.1 no streaming radio if static address

[Tim Curtis]

I can confirm that as of 9.0.4 64-bit Curl fails for radio station lookup when static ip used, but succeeds with dhcp. pi 3b+

    John

Post both the static and DHCP entries listed in the startup log (moodeutl -l). You will need to configure static then reboot and copy the entries from the log, then configure DHCP and do same.

Most problems with static addressing are caused by incorrect Netmask or missing/incorrect DNS entries.

I've tested static addressing many times on my end and no issues whatsoever but I can never rule out bugs.

[Listener]

I can confirm that as of 9.0.4 64-bit Curl fails for radio station lookup when static ip used, but succeeds with dhcp. pi 3b+

    John

Post both the static and DHCP entries listed in the startup log (moodeutl -l). You will need to configure static then reboot and copy the entries from the log, then configure DHCP and do same.

Most problems with static addressing are caused by incorrect Netmask or missing/incorrect DNS entries.

I've tested static addressing many times on my end and no issues whatsoever but I can never rule out bugs.

I can do more later, but this for now as I no longer know how to log into the ssh terminal since the credentials pi and moodaudio stopped working


192.168.1.10 moode
192.168.1.1 gateway
255.255.255.0 netmask
8.8.8.8 dns1
8.8.4.4 dns2
worked for 8.x

Best,

    John

    john -- who doesn't know how to

[TheOldPresbyope]

@Listener 

I'm betting that your router/ISP support IPv6 as well as IPv4 and that you're hitting the same snag I reported last month in this thread.

What is the content of the file /etc/resolv.conf when your networking interface address methods are set for DHCP and again when set for Static addressing? (Yes, you'll have to go to the command line to get this info; it's not in the log.)

Regards,
Kent

[Listener]

A field report.

Due to the problems with static ips, I switched to dynamic ips and name addressing, moodexxx.local for my moode boxes where xxx is the designator of that machine such as moodegarage.local. That works perfectly but may point to a problem. With static ips the initial load time for moode is MUCH longer than when names are used, names being perhaps 10 times faster. I have verified this by switching back and forth. There are no problems on my lan that I am aware of, all the other devices, some 20 of them, work as expected, some using fixed ips and some dynamic. The space from 192.168.1.1 to 192.168.1.100 is reserved for static ips. The rest of the address space is available for dynamic.

Happy listening,

John

[mathieuruellan]

Hello, i've got something weird with ipv6.
All my devices work like a charm with ipv6 sinces many years (My ISP free.fr supports ipv6 since decades).
I could connect to the moode rpi with ssh on the ipv6 address, and in the pi console i can ping -6 websites outside.
BUT, the moode spotify endpoint appears on clients (android, linux client - on the same lan) a few seconds on start and disappears after 2 or 3 seconds.
And avahi-browse still detects the advertisement.

I've disable ipv6 on the pi and now it works fine. But I don't understand what was the pb. If someone have an idea....