Thanks for that additional info, I have some feedback for you if you would like to look into this further:
The trial is not an issue, I will reach out via private message regarding this.
I believe the Docker aspect might be playing a part into this issue. If you install RoonServer on Ubuntu nativity it would be much easier to troubleshoot.
According to the logs you sent, it looks like Roon is trying to use a busy socket, maybe Docker is using it for something else so checking on native Ubuntu will be a good step in the right direction, you can install Roon there by using our Linux Install Instructions.
Thanks for confirming that this behavior occurs on the regular Ubuntu setup and not in Docker. I believe it’s best if we try using a different Core to determine weather the Ubuntu networking settings is playing a part in this behavior.
Would it be possible for you to temporarily host the Roon Core on one of your MacOS laptops and let us know if the issue is the same there? This should help clarify if this issue is related to the Core or elsewhere on the network.
You can assign the MacOS as the Core by installing Roon on it, and on the “Choose your Core” page select “Use this PC” (instead of connecting to the Ubuntu Core). You may be presented with an “Authorizations” screen and be prompted to un-authorize the Ubuntu Core, there are no adverse affects for switching between Cores and you can do so as many times as you wish, but you are limited to just one “active” Roon Core at a time.
Installed Roon on my MBPro. Mounted the same songs off my Synology and things seem much better. Meaning: things play without a hitch for the most part. Occasionally some brief pauses mid-song which may just be wifi network congestion or whatever, but at least songs seem to play pretty consistently.
Glad to hear the MacBook is working out better for you. Since switching the Core helped here, something about the initial Ubuntu setup is affecting Roon adversely. I can’t comment on where exactly things are going wrong with the routing on Ubuntu, but you may want to take a closer look there or keep the Core on the Mac/a different platform.
So can you explain these log messages I reporter earlier???
Basically, it looks to me like Roon tried (and failed) establishing a new airplay/RTSP connection to my AppleTV named “Home Theater” at 172.16.2.1 on TCP port 7000. That AppleTV device has a MAC address of 08:66:98:f3:af:c1 which corresponds to the “DeviceId” in the log as well as being named “Home Theater”.
Is that your reading of those log messages too or am I misunderstanding them?
So the problem then isn’t that the port has a conflict then (TCP source ports are random). The issue is that Roon for some reason is using the wrong destination IP address for the AppleTV. The AppleTV is at 172.16.1.157 not 172.16.2.1.
172.16.2.1 is the firewall to the internet. So why is Roon trying to talk to the firewall when it’s supposed to be talking to the AppleTV? As I explained earlier, the Ubuntu Core box has an IP of 172.16.1.100 - so it can talk directly to the AppleTV and doesn’t need to go through the firewall. Also, the Core correctly discovered the IP address of the AppleTV based on the configuration:
For clarity, the Ubuntu Core box is multi-homed- meaning it has multiple IP addresses assigned to it (172.16.2.100/24 and 172.16.1.100/24). My MacBookPro only has an IP address on the 172.16.1.0/24 network so maybe that’s why Roon isn’t confused on my Mac, but if Roon is confused by this, that as best as I can tell is a bug in Roon. That or maybe someone who understands the Apple Airplay/RTSP protocol can guess what is going on?
Thanks for clarifying the issue and for letting me know about the multiple subnets/interfaces here. I have discussed your case with our senior technical team today and we believe that this is the main cause of the issue here:
Testing Roon on multiple network interfaces is not something we typically do, but in this case we are going to try and reproduce your findings in the lab and see if there is a bug here we can address.
Can I please request you share some more information on how you have the multiple IPs assigned to the Ubuntu Core? Are you using two different Network Adapters or are they configured virtually? What kind of firewall are you using, just the USG or something else as well?
Sadly, since all (well both of them) my OS X boxes are laptops- mine and my wife’s. My wife shuts her laptop down when not in use and I travel/etc. As you can imagine, explaining to my wife she can’t listen to music when I’m not around because I took the music server with me isn’t gonna fly.
Anyways, I’ve got a few more weeks on my free trial; so hopefully you’re able to look into this before it expires. Let me know if I can be of any more assistance.
So honestly, I never got it working. Roon extended my eval lic a few times and we got nowhere.
FWIW, I think the problem was my roon server was multi-homed on multiple subnets and that was causing confusions with the multicast announcements. Roon never contacted me to try any fixes they might of cooked up.
I’ve actually recently re-designed my network and traffic is now routed between networks and none of my hosts are multi-homed anymore. I’m kinda curious if that fixes the problem, but I’ve never bothered to reach out to Roon again for another eval lic.