Solved: Radio Station not working

[SOLVED] Radio Station not working - 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] Radio Station not working (/showthread.php?tid=7328)

Pages: 1 2

RE: Radio Station not working - kosi123 - 01-20-2025

Code:
20250118 103125 worker: -- Network

20250118 103125 worker: --

20250118 103125 worker: Eth0

20250118 103125 worker: Ethernet: adapter does not exist

20250118 103125 worker: Wlan0

20250118 103125 worker: Wireless: adapter exists

20250118 103125 worker: Wireless: country AT

20250118 103125 worker: Wireless: SSID    K6

20250118 103125 worker: Wireless: other   None

20250118 103125 worker: Wireless: timeout up to 90 secs

20250118 103126 worker: Wireless: connect to K6

20250118 103126 worker: Wireless: method  dhcp

20250118 103126 worker: Wireless: address 192.168.2.134

20250118 103126 worker: Wireless: netmask 255.255.255.0

20250118 103126 worker: Wireless: gateway 192.168.2.1

20250118 103126 worker: Wireless: pri DNS 192.168.2.1

20250118 103126 worker: Wireless: domain  intern-linz

20250118 103126 worker: --

This is the output. Doubt it's an issue with moode though - like previously mentioned I just discovered my laptop has the issue as well. I must apologize for posting here, in the beginning I thought it was an issue with moode since the BluOS speaker works.

RE: Radio Station not working - Tim Curtis - 01-20-2025

(01-20-2025, 08:52 PM)kosi123 Wrote:
Code:
20250118 103125 worker: -- Network 20250118 103125 worker: -- 20250118 103125 worker: Eth0 20250118 103125 worker: Ethernet: adapter does not exist 20250118 103125 worker: Wlan0 20250118 103125 worker: Wireless: adapter exists 20250118 103125 worker: Wireless: country AT 20250118 103125 worker: Wireless: SSID K6 20250118 103125 worker: Wireless: other None 20250118 103125 worker: Wireless: timeout up to 90 secs 20250118 103126 worker: Wireless: connect to K6 20250118 103126 worker: Wireless: method dhcp 20250118 103126 worker: Wireless: address 192.168.2.134 20250118 103126 worker: Wireless: netmask 255.255.255.0 20250118 103126 worker: Wireless: gateway 192.168.2.1 20250118 103126 worker: Wireless: pri DNS 192.168.2.1 20250118 103126 worker: Wireless: domain intern-linz 20250118 103126 worker: --

This is the output. Doubt it's an issue with moode though - like previously mentioned I just discovered my laptop has the issue as well. I must apologize for posting here, in the beginning I thought it was an issue with moode since the BluOS speaker works.

No prob. The network settings look ok.

RE: Radio Station not working - Nutul - 01-20-2025

Are you connected to a VPN???

RE: Radio Station not working - TheOldPresbyope - 01-21-2025

@kosi123

Here in the US with my ISP service, I can resolve and play the FM4 URL. Using the Linux dig command I find that orf-live.ors-shoutcast.at resolves to the following host IPs (in the fifth column)

Code:
orf-live.ors-shoutcast.at. 1    IN    A    109.70.96.178

orf-live.ors-shoutcast.at. 1    IN    A    92.60.12.148

orf-live.ors-shoutcast.at. 1    IN    A    92.60.12.147

orf-live.ors-shoutcast.at. 1    IN    A    92.60.12.146

orf-live.ors-shoutcast.at. 1    IN    A    109.70.96.180

orf-live.ors-shoutcast.at. 1    IN    A    81.16.149.156

orf-live.ors-shoutcast.at. 1    IN    A    109.70.96.179

orf-live.ors-shoutcast.at. 1    IN    A    185.81.213.122

orf-live.ors-shoutcast.at. 1    IN    A    185.81.213.126

orf-live.ors-shoutcast.at. 1    IN    A    185.81.213.123

orf-live.ors-shoutcast.at. 1    IN    A    81.16.149.155

orf-live.ors-shoutcast.at. 1    IN    A    81.16.149.154

If you can ping these addresses from the command line of your moOde player, then it's only DNS which is tripping you up.

Example: choosing one of the IPs at random, here's a successful ping (the -c1 option means one ping only)

Code:
rho@m922green:~ $ ping -c1 81.16.149.156

PING 81.16.149.156 (81.16.149.156) 56(84) bytes of data.

64 bytes from 81.16.149.156: icmp_seq=1 ttl=52 time=114 ms

--- 81.16.149.156 ping statistics ---

1 packets transmitted, 1 received, 0% packet loss, time 0ms

rtt min/avg/max/mdev = 114.190/114.190/114.190/0.000 ms

Your startup log shows you are provisioning your wireless adapter parameters through DHCP; that service has also configured it to use your gateway (192.168.2.1) as your DNS server. In fact, the gateway is just forwarding DNS requests from your player to your ISP's DNS servers.

If you can successfully ping the IP addresses above, you could try the following to bypass your ISPs DNS. NOTE - you'll have to choose a IP address which isn't in use. On my router, I have configured my router to reserve a small segment of IP addresses as not assignable via DHCP so I can assign them statically. That prevents accidental collisions. YMMV.

On with the show:

On the Networking config screen, change the wireless addressing method from DHCP to static. A new block of options will appear below the access point block.

Address: enter your chosen static IP address (somewhere in the range 192.168.2.2-254; maybe 192.168.2.250)
Netmask: 255.255.255.0
Gateway: 192.168.2.1
Primary DNS: I usually use 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
Secondary DNS: I use the one I didn't choose as primary

Be sure to save and reboot. Now you should be able to reach FM4. I just did this here and I can still reach FM4 (and all other radio stations) so at least it doesn't break a working system.

If for some reason your moOde player boots up but you can't reach it either by hostname or by the static IP address you entered above, and if it also doesn't come up as a hotspot, you can connect temporarily via Ethernet cable in order to revert the settings to DHCP. (It's possible to recover by editing your uSD card on another host but that's really getting into Linux-fu).

Regards,
Kent

RE: Radio Station not working - kosi123 - 01-21-2025

Thank you. This solved it for me.

Before doing the static IP and that stuff, I reached out to my ISP and asked them about it. They told me it wasn't a problem on their side.

However, specifying a DNS server (I used google and cloudflare, as suggested) did the trick and now it works. Seems like it was a problem with my ISP after all...

Thank you very much for your help!

As for why it worked on the BluOS device, I can only guess - but my best one would be that there is a custom DNS specified by default?