KIMB-technologies/Radio-API

Sonoro radio not supported?

alfureu opened this issue · 4 comments

alfureu commented

Tip

Please also see Troubleshooting.

Radio-API Installation

  • Version of Radio-API: latest
  • Installation mode: Docker
  • DNS redirect via: tried with and without
  • Radio vendor: Sonoro
  • Usage of reverse proxy: no
  • Does another radio use your installation of Radio-API: no

Describe the Issue
Received a Sonoro Stream radio, noticed the expiration of the link for stream radio on the website, so I found your project. The docker runs successfully, I get to the GUI code website. However, I am not able to get the GUI code from the radio. I did a tcpdump during the connection, and see the part, whenever I try to get a station list

The 2 most important environments in the docker-compose.yml are set as follows:

      - CONF_DOMAIN=http://wifiradiofrontier.com/ # the domain where the system is hosted
      - CONF_RADIO_DOMAIN=http://sonoro.wifiradiofrontier.com # different domain to use for connections of the radio (if set CONF_DOMAIN is for GUI)

Am I doing something wrong?

Error Message or Log Files

23:45:41.895181 IP (tos 0x0, ttl 64, id 50777, offset 0, flags [none], proto UDP (17), length 90)
    192.168.250.254.53 > 192.168.250.29.50895: [bad udp cksum 0x76c5 -> 0x7998!] 7 ServFail q: A? sonoro.wifiradiofrontier.com. 1/0/0 sonoro.wifiradiofrontier.com. [8h15m8s] A 217.33.180.98 (62)
23:45:41.902998 IP (tos 0x0, ttl 60, id 236, offset 0, flags [none], proto UDP (17), length 75)
    192.168.250.29.50896 > 192.168.250.254.53: [udp sum ok] 8+ A? sonoro2.wifiradiofrontier.com. (47)
23:45:41.926911 IP (tos 0x0, ttl 64, id 50778, offset 0, flags [none], proto UDP (17), length 91)
    192.168.250.254.53 > 192.168.250.29.50896: [bad udp cksum 0x76c6 -> 0xead8!] 8 ServFail q: A? sonoro2.wifiradiofrontier.com. 1/0/0 sonoro2.wifiradiofrontier.com. [11m2s] A 217.33.180.97 (63)
23:45:43.475659 IP (tos 0x0, ttl 60, id 237, offset 0, flags [none], proto UDP (17), length 74)
    192.168.250.29.50897 > 192.168.250.254.53: [udp sum ok] 9+ A? sonoro.wifiradiofrontier.com. (46)
23:45:43.500623 IP (tos 0x0, ttl 64, id 50876, offset 0, flags [none], proto UDP (17), length 90)
    192.168.250.254.53 > 192.168.250.29.50897: [bad udp cksum 0x76c5 -> 0x7995!] 9 ServFail q: A? sonoro.wifiradiofrontier.com. 1/0/0 sonoro.wifiradiofrontier.com. [8h15m7s] A 217.33.180.98 (62)
23:45:43.511639 IP (tos 0x0, ttl 60, id 238, offset 0, flags [none], proto UDP (17), length 75)
    192.168.250.29.50898 > 192.168.250.254.53: [udp sum ok] 10+ A? sonoro2.wifiradiofrontier.com. (47)
23:45:43.536196 IP (tos 0x0, ttl 64, id 50879, offset 0, flags [none], proto UDP (17), length 91)
    192.168.250.254.53 > 192.168.250.29.50898: [bad udp cksum 0x76c6 -> 0xebd4!] 10 ServFail q: A? sonoro2.wifiradiofrontier.com. 1/0/0 sonoro2.wifiradiofrontier.com. [11m1s] A 217.33.180.97 (63)
23:45:45.981796 IP (tos 0x0, ttl 60, id 239, offset 0, flags [none], proto UDP (17), length 74)
    192.168.250.29.50899 > 192.168.250.254.53: [udp sum ok] 11+ A? sonoro.wifiradiofrontier.com. (46)
23:45:46.006766 IP (tos 0x0, ttl 64, id 50978, offset 0, flags [none], proto UDP (17), length 90)
    192.168.250.254.53 > 192.168.250.29.50899: [bad udp cksum 0x76c5 -> 0x7994!] 11 ServFail q: A? sonoro.wifiradiofrontier.com. 1/0/0 sonoro.wifiradiofrontier.com. [8h15m4s] A 217.33.180.98 (62)
23:45:46.009885 IP (tos 0x0, ttl 60, id 240, offset 0, flags [none], proto UDP (17), length 75)
    192.168.250.29.50900 > 192.168.250.254.53: [udp sum ok] 12+ A? sonoro2.wifiradiofrontier.com. (47)
23:45:46.034061 IP (tos 0x0, ttl 64, id 50981, offset 0, flags [none], proto UDP (17), length 91)
    192.168.250.254.53 > 192.168.250.29.50900: [bad udp cksum 0x76c6 -> 0xeed0!] 12 ServFail q: A? sonoro2.wifiradiofrontier.com. 1/0/0 sonoro2.wifiradiofrontier.com. [10m58s] A 217.33.180.97 (63)
23:45:47.430817 IP (tos 0x0, ttl 1, id 241, offset 0, flags [none], proto UDP (17), length 155)
    192.168.250.29.57040 > 239.255.255.250.1900: [udp sum ok] UDP, length 127
23:45:47.576991 IP (tos 0x0, ttl 60, id 242, offset 0, flags [none], proto UDP (17), length 74)
    192.168.250.29.50901 > 192.168.250.254.53: [udp sum ok] 13+ A? sonoro.wifiradiofrontier.com. (46)
23:45:47.601526 IP (tos 0x0, ttl 64, id 51021, offset 0, flags [none], proto UDP (17), length 90)
    192.168.250.254.53 > 192.168.250.29.50901: [bad udp cksum 0x76c5 -> 0x7991!] 13 ServFail q: A? sonoro.wifiradiofrontier.com. 1/0/0 sonoro.wifiradiofrontier.com. [8h15m3s] A 217.33.180.98 (62)
23:45:47.604721 IP (tos 0x0, ttl 60, id 243, offset 0, flags [none], proto UDP (17), length 75)
    192.168.250.29.50902 > 192.168.250.254.53: [udp sum ok] 14+ A? sonoro2.wifiradiofrontier.com. (47)
23:45:47.628718 IP (tos 0x0, ttl 64, id 51023, offset 0, flags [none], proto UDP (17), length 91)
    192.168.250.254.53 > 192.168.250.29.50902: [bad udp cksum 0x76c6 -> 0xefcc!] 14 ServFail q: A? sonoro2.wifiradiofrontier.com. 1/0/0 sonoro2.wifiradiofrontier.com. [10m57s] A 217.33.180.97 (63)
23:45:48.632817 IP (tos 0x0, ttl 255, id 244, offset 0, flags [none], proto UDP (17), length 532)
    192.168.250.29.5353 > mdns.mcast.net.5353: [udp sum ok] 0*- [0q] 10/0/4 sonoroSTREAM 30589088d044._undok._tcp.local. (Cache flush) [1h15m] TXT "VendorID=undok" "DeviceInfoLocation=/dd.xml" "FsAPILocation=/fsapi", _services._dns-sd._udp.local. [1h15m] PTR _undok._tcp.local., _undok._tcp.local. [1h15m] PTR sonoroSTREAM 30589088d044._undok._tcp.local., 29.250.168.192.in-addr.arpa. (Cache flush) [2m] PTR sonoroSTREAM-30589088d044.local., sonoroSTREAM 30589088d044._spotify-connect._tcp.local. (Cache flush) [1h15m] TXT "CPath=/goform/spotifyConfig" "VERSION=1.0", _services._dns-sd._udp.local. [1h15m] PTR _spotify-connect._tcp.local., _spotify-connect._tcp.local. [1h15m] PTR sonoroSTREAM 30589088d044._spotify-connect._tcp.local., sonoroSTREAM 30589088d044._undok._tcp.local. (Cache flush) [2m] SRV sonoroSTREAM-30589088d044.local.:80 0 0, sonoroSTREAM-30589088d044.local. (Cache flush) [2m] A 192.168.250.29, sonoroSTREAM 30589088d044._spotify-connect._tcp.local. (Cache flush) [2m] SRV sonoroSTREAM-30589088d044.local.:80 0 0 ar: sonoroSTREAM 30589088d044._undok._tcp.local. (Cache flush) [1h15m] NSEC, 29.250.168.192.in-addr.arpa. (Cache flush) [2m] NSEC, sonoroSTREAM 30589088d044._spotify-connect._tcp.local. (Cache flush) [1h15m] NSEC, sonoroSTREAM-30589088d044.local. (Cache flush) [2m] NSEC (504)
23:45:52.260203 IP (tos 0x0, ttl 60, id 245, offset 0, flags [none], proto UDP (17), length 74)
    192.168.250.29.50903 > 192.168.250.254.53: [udp sum ok] 15+ A? sonoro.wifiradiofrontier.com. (46)
23:45:52.285362 IP (tos 0x0, ttl 64, id 51257, offset 0, flags [none], proto UDP (17), length 90)
    192.168.250.254.53 > 192.168.250.29.50903: [bad udp cksum 0x76c5 -> 0x7992!] 15 ServFail q: A? sonoro.wifiradiofrontier.com. 1/0/0 sonoro.wifiradiofrontier.com. [8h14m58s] A 217.33.180.98 (62)
23:45:52.288760 IP (tos 0x0, ttl 60, id 246, offset 0, flags [none], proto UDP (17), length 75)
    192.168.250.29.50904 > 192.168.250.254.53: [udp sum ok] 16+ A? sonoro2.wifiradiofrontier.com. (47)
23:45:52.313829 IP (tos 0x0, ttl 64, id 51259, offset 0, flags [none], proto UDP (17), length 91)
    192.168.250.254.53 > 192.168.250.29.50904: [bad udp cksum 0x76c6 -> 0xf4c8!] 16 ServFail q: A? sonoro2.wifiradiofrontier.com. 1/0/0 sonoro2.wifiradiofrontier.com. [10m52s] A 217.33.180.97 (63)
23:45:57.450231 IP (tos 0x0, ttl 1, id 247, offset 0, flags [none], proto UDP (17), length 155)
    192.168.250.29.57040 > 239.255.255.250.1900: [udp sum ok] UDP, length 127
kimbtech commented

Hi,
based on the logs it seems that DNS queries are not altered correctly.

The Radio gets the IP addresses 217.33.180.97 and 217.33.180.98 for the domains sonoro2.wifiradiofrontier.com and sonoro.wifiradiofrontier.com.
These IP addresses seem to be the default ones run by Frontier N., i.e., the radio does not send the request to Radio-API and thus does not show the GUI code.

Do you use Radio-DNS (https://github.com/KIMB-technologies/Radio-DNS-Server) as described in 1. https://github.com/KIMB-technologies/Radio-API/blob/master/Setup.md#setup-using-docker?

Do you see requests of the radio when you run docker-compose logs with Radio-API?

alfureu commented

Thanks for the guidance, you were right, I needed to redirect both sonoro.* and sonoro2.* DNS records and it started to work. I just need to give an exception for time.wifiradiofrontier.com for the proper NTP update.

By the way, for the logos, would it be possible to introduce SVG support?

kimbtech commented

Hi,
glad that it works now.

The images are rendered by the radio itself and Radio-API just forwards the links. Thus, svg support would need to introduced by frontier silicon.

kimbtech commented

Hi,
I just added an update providing a radio station logo cache. This cache als converts SVG images to PNGs images, s.t., the radio can display them.

  • 👍2