Moode Forum
[SOLVED] Moode 9.0.1 no streaming radio if static address - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [SOLVED] Moode 9.0.1 no streaming radio if static address (/showthread.php?tid=6556)

Pages: 1 2 3

Moode 9.0.1 no streaming radio if static address - hronists - 06-04-2024

It took me a while to figure out why I cannot start any radio stream or spotify connect until I changed wifi network connection from static to DHCP. I can live with DHCP, but I rather have static addresses for some devices. 

Alert

Failed to decode http://ice1.somafm.com/indiepop-128-aac; CURL failed: Could not resolve host: ice1.somafm.com

RE: Moode 9.0.1 no streaming radio if static address - tanki - 06-04-2024

Hi

when you set a static IP do you also set nameservers and gateway ?

what is the output of
Code:
ip route show
and
Code:
cat /etc/resolv.conf
while network is configured with a static IP ?

RE: Moode 9.0.1 no streaming radio if static address - Tim Curtis - 06-04-2024

The symptom suggests a network configuration issue.

Reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

RE: Moode 9.0.1 no streaming radio if static address - hronists - 06-05-2024

Log file with static IP address:

Code:
20240605 171925 worker: Wireless: country LV
20240605 171925 worker: Wireless: SSID    lynx5
20240605 171925 worker: Wireless: other   None
20240605 171925 worker: Wireless: timeout up to 90 secs
20240605 171925 worker: Wireless: connect to lynx5
20240605 171925 worker: Wireless: method  static
20240605 171925 worker: Wireless: address 192.168.1.120
20240605 171925 worker: Wireless: netmask 255.255.255.0
20240605 171925 worker: Wireless: gateway 192.168.1.254
20240605 171925 worker: Wireless: pri DNS none found
20240605 171925 worker: Wireless: domain  none found

I tried 192.168.1.254, 1.1.1.1, 8.8.8.8 - message is always: pri DNS none found

Log file with DHCP:


Code:
20240604 201207 worker: Wlan0
20240604 201208 worker: Wireless: adapter exists
20240604 201208 worker: Wireless: country LV
20240604 201208 worker: Wireless: SSID    lynx5
20240604 201208 worker: Wireless: other   None
20240604 201208 worker: Wireless: timeout up to 90 secs
20240604 201208 worker: Wireless: connect to lynx5
20240604 201208 worker: Wireless: method  dhcp
20240604 201208 worker: Wireless: address 192.168.1.137
20240604 201208 worker: Wireless: netmask 255.255.255.0
20240604 201208 worker: Wireless: gateway 192.168.1.254
20240604 201208 worker: Wireless: pri DNS 192.168.1.254
20240604 201208 worker: Wireless: domain  none found


RE: Moode 9.0.1 no streaming radio if static address - Tim Curtis - 06-05-2024

That might be a bug in the log entry. I'll investigate.

With static address specified including primary dns of 192.168.1.254, save the config (in Network Config) and then post the contents of the nmconnect file

sudo cat /etc/NetworkManager/system-connections/lynx5.nmconnection. Feel free to replace the psk with x's.

ETA: also post contents of file below

cat /etc/resolv.conf

RE: Moode 9.0.1 no streaming radio if static address - hronists - 06-05-2024

Here it is

Code:
[connection]
id=lynx5
uuid=3607a669-f8e2-450f-a131-a06c74073aca
type=wifi
interface-name=wlan0
autoconnect=true
autoconnect-priority=100
[wifi]
mode=infrastructure
ssid=lynx5
hidden=false
[wifi-security]
key-mgmt=wpa-psk
psk=
[ipv4]
method=manual
address1=192.168.1.120/24
gateway=192.168.1.254
dns=192.168.1.254,8.8.8.8
[ipv6]
addr-gen-mode=default
method=auto


And then I removed secondary DNS server

Code:
[connection]
id=lynx5
uuid=a939aa58-51cb-4da7-a639-e4b1b3b7437c
type=wifi
interface-name=wlan0
autoconnect=true
autoconnect-priority=100
[wifi]
mode=infrastructure
ssid=lynx5
hidden=false
[wifi-security]
key-mgmt=wpa-psk
psk=
[ipv4]
method=manual
address1=192.168.1.120/24
gateway=192.168.1.254
dns=192.168.1.254
[ipv6]
addr-gen-mode=default
method=auto

And it works ok with static IP address now.

It looks like the issue was with secondary DNS.

And startup log once again - primary DNS is there:

Code:
20240605 182139 worker: Wlan0
20240605 182139 worker: Wireless: adapter exists
20240605 182139 worker: Wireless: country LV
20240605 182139 worker: Wireless: SSID    lynx5
20240605 182139 worker: Wireless: other   None
20240605 182139 worker: Wireless: timeout up to 90 secs
20240605 182139 worker: Wireless: connect to lynx5
20240605 182139 worker: Wireless: method  static
20240605 182139 worker: Wireless: address 192.168.1.120
20240605 182139 worker: Wireless: netmask 255.255.255.0
20240605 182139 worker: Wireless: gateway 192.168.1.254
20240605 182139 worker: Wireless: pri DNS 192.168.1.254
20240605 182139 worker: Wireless: domain  none found


RE: Moode 9.0.1 no streaming radio if static address - TheOldPresbyope - 06-05-2024

I suspect the problems may run deeper.

When Tim started porting moOde to Bookworm, I played with the new networking managment (cleverly known as NetworkManager) and thought that static addressing in moOde was working correctly. Tim's ETA just now to post /etc/resolv.conf made me look and I discovered I wasn't paying attention.

Background - my ISP is Comcast and I'm running a Comcast-provided cable modem/router/access point. Comcast supports both IPv4 and IPv6 (at least it does in my location in Maryland).

Yes, I just configured the moOde WiFi connection to a static IPv4 address, IPv4 gateway address, and external IPv4 DNS addresses (Cloudflare and Google) and rebooted. Everything seemed to be working fine. Radio stations play. The IPv4 addresses are all shown properly in the nmconnection file and in the moode information outputs.

However, look at the last stanza of your nmconnection file (which reads the same as mine)


Code:
[ipv6]
addr-gen-mode=default
method=auto

This means our players will still get DHCP-assigned IPv6 addresses (if your router provides them, as mine does).

So, my moOde WiFi interface is running on the IPv4 address I assigned and also the IPv6 address my router assigned. More importantly, the /etc/resolv.conf file shows *only* the IPv6 addresses of the Comcast DNS servers irrespective of my choice of static or DHCP addressing.

Regards,
Kent

RE: Moode 9.0.1 no streaming radio if static address - Tim Curtis - 06-05-2024

Is there an issue I need to look at?

RE: Moode 9.0.1 no streaming radio if static address - TheOldPresbyope - 06-05-2024

(06-05-2024, 05:43 PM)Tim Curtis Wrote: Is there an issue I need to look at?

Maybe, but I haven’t got a good definition of just what it is. 

Just now tried to kill the IPv6 interface by changing the stanza in the nmconnection file, using nmcli, and rebooting. Something changed the nmconnection file back and the IPv6 interface is up with DHCP-assigned settings.???

ETA- I was doing this to see what would if there were no DNS settings available via the router's IPv6 DHCP service.

Regards,
Kent

RE: Moode 9.0.1 no streaming radio if static address - Tim Curtis - 06-05-2024

I think I see that if ipv4 is set to static, ipv6 method=auto could prolly create some sort of weird conflict.

[ipv6]
addr-gen-mode=default
method=auto

According to the spec for nmconnect files "disabled" is an option for method.

Code:
IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.