This weekend I tried 6 different configurations for Roon:
NUC + ROCK
NUC + Linux Mint + Roon Server
NUC + Ubuntu Server + Roon Server
Fujitsu Laptop + Linux Mint + Roon Server
Fujitsu Laptop + Window 10 Pro + Roon App
Fujitsu Laptop + Window 10 Pro + Roon Server
What can I say, Windows is the less problematic system in my case.
Didn’t notice any skips, only a few slow loading tracks. But I don’t like Windows. And I don’t want to buy extra license for it to install on NUC, because I’m not sure that this will fix all issues.
ROCK is the worst, surprisingly and unfortunately.
Now I’m on Laptop + Linux Mint + Roon Server, but I made some tricks.
I read that it could be specific global (national) firewall issues.
Some Amazon IPs are blocked.
Some users can fix it by adding their own firewall rules and block these IPs locally on the router with “reject” parameter, not “drop”
So Roon can immediately switch to another.
But these IPs change from time to time.
So, what I did: I manually add one firewall rule to iptables on Linux Mint: sudo iptables-legacy -A OUTPUT -p tcp -d 22.214.171.124 -j REJECT
+ sudo iptables-legacy-save
to save the rule
This is the exact problem IP address for now.
6 month ago that address was 126.96.36.199
(Maybe I should add this address to that reject rule too. Unsure)
I left Roon to play 24 hours playlist in the background and this evening I will check if there will be any skips. (8 hours it’s ok so far)
If it work, I will move to NUC + Linux Mint + Roon Server + this firewall rule.
This is not elegant and not universal solution, but it works so far. Until another IP will be blocked.
Anyway, it doesn’t explain why Qobuz in Roon and Tidal itself work fine.
I think the issue must be solved somehow inside Roon.
And I hope that my sitiation will help Roon to fix that uncertain issues with Tidal or ROCK or Linux Roon Server.
My second setup:
Roon Core - Intel NUC 8i5BEH2 (16Gb RAM, 512Gb M.2 SSD) - ROCK Version 1.0 (build 227) stable, Roon Server Version 1.8 (build 814) stable
Roon endpoint - KEF LS50 Wireless
Network Router - ASUS RT-N65U
Core connected directly to router via ethernet cable
KEFs - via WiFi
DNS - 188.8.131.52
The same issues as I already described here and here right in time when I’m posting this
I can see in router log that ROCK and Roon Remote can’t acces a dozen of IPs with “TIME_WAIT” state
These IPs are:
Thanks for the additional details here! Let me discuss your findings with the QA team. Can you please confirm - if you by any chance have a VPN or mobile hotspot, does the same issue occur? Or does the issue only occur on your home network?
No, I don’t have any VPN. As I said earlier when I block (reject) 184.108.40.206 address Roon starts to function more or less stable.
But I can do it only if I’m on my main setup. Now I use Microtik router instead of TP-Link and it makes possible to add that specific firewall rule:
If it will be helpful, here are ping and traceroute results from ASUS:
PING 220.127.116.11 (18.104.22.168): 56 data bytes
64 bytes from 22.214.171.124: seq=0 ttl=107 time=139.543 ms
64 bytes from 126.96.36.199: seq=1 ttl=108 time=138.375 ms
64 bytes from 188.8.131.52: seq=2 ttl=107 time=138.365 ms
64 bytes from 184.108.40.206: seq=3 ttl=107 time=138.378 ms
64 bytes from 220.127.116.11: seq=4 ttl=107 time=138.789 ms
--- 18.104.22.168 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 138.365/138.690/139.543 ms
traceroute to 22.214.171.124 (126.96.36.199), 30 hops max, 38 byte packets
1 188.8.131.52 (184.108.40.206) 4.870 ms 5.252 ms 5.820 ms
2 220.127.116.11 (18.104.22.168) 4.165 ms 3.618 ms 10.063 ms
3 22.214.171.124 (126.96.36.199) 18.072 ms 188.8.131.52 (184.108.40.206) 16.992 ms 17.208 ms
4 220.127.116.11 (18.104.22.168) 16.775 ms 22.214.171.124 (126.96.36.199) 16.827 ms 188.8.131.52 (184.108.40.206) 17.558 ms
5 220.127.116.11 (18.104.22.168) 62.226 ms 22.214.171.124 (126.96.36.199) 16.927 ms 188.8.131.52 (184.108.40.206) 17.242 ms
6 220.127.116.11 (18.104.22.168) 34.494 ms 34.378 ms 22.214.171.124 (126.96.36.199) 35.351 ms
7 188.8.131.52 (184.108.40.206) 49.799 ms 220.127.116.11 (18.104.22.168) 48.963 ms 22.214.171.124 (126.96.36.199) 48.314 ms
8 * 188.8.131.52 (184.108.40.206) 129.559 ms 134.152 ms
9 220.127.116.11 (18.104.22.168) 139.408 ms 22.214.171.124 (126.96.36.199) 138.892 ms 188.8.131.52 (184.108.40.206) 139.593 ms
10 220.127.116.11 (18.104.22.168) 139.389 ms 22.214.171.124 (126.96.36.199) 151.552 ms 138.091 ms
11 188.8.131.52 (184.108.40.206) 139.203 ms 220.127.116.11 (18.104.22.168) 139.525 ms 22.214.171.124 (126.96.36.199) 138.906 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * 188.8.131.52.bc.googleusercontent.com (184.108.40.206) 138.015 ms 138.465 ms
Thank you for those additional details, I spoke to the QA team and we are looking into your report. Can you please confirm my previously asked question? If you try to use a mobile Hotspot, do you still see the issue occur when connecting that way? Or does the issue only occur on your current ISP network? Thanks!