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?
Yes, that looks about right based on the log. Do you have anything else using port 7000 on your Core/Apple TV? Perhaps an Emby/Plex server or some other kind of server?
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?
Hi @Aaron_Turner,
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?
One physical NIC, but two logical networks (VLAN’s):
$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 9920841 bytes 4793692893 (4.7 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9920841 bytes 4793692893 (4.7 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p3p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.1.100 netmask 255.255.255.0 broadcast 172.16.1.255
inet6 fe80::feaa:14ff:fedc:9396 prefixlen 64 scopeid 0x20<link>
ether fc:aa:14:dc:93:96 txqueuelen 1000 (Ethernet)
RX packets 121897244 bytes 123264994650 (123.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 106640527 bytes 118595095376 (118.5 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p3p1.100: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.2.100 netmask 255.255.255.0 broadcast 172.16.2.255
inet6 fe80::feaa:14ff:fedc:9396 prefixlen 64 scopeid 0x20<link>
ether fc:aa:14:dc:93:96 txqueuelen 1000 (Ethernet)
RX packets 5002070 bytes 1268848214 (1.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 296707 bytes 30284347 (30.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ ip route
default via 172.16.1.1 dev p3p1 onlink
172.16.1.0/24 dev p3p1 proto kernel scope link src 172.16.1.100
172.16.2.0/24 dev p3p1.100 proto kernel scope link src 172.16.2.100
So the untagged interface is 172.16.1.100 and the tagged (vlan100) is 172.16.2.100.
I have my home network broken up across a few networks and the Ubuntu server is on two of them. The USG is also on both (172.16.1.1 and 172.16.2.1) while the AppleTV is only on 172.16.1.157.
Thanks for the additional info @Aaron_Turner, I have added it to the case notes.
QA will try to reproduce as I mentioned, but this may take some time to track down and I can’t comment on exactly when it will reach the queue.
In the meantime, if the MacOS is working as expected I suggest you use this for the time being. Thanks!
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.
Just got the notification that my free trial is about to expire. Any luck reproducing/fixing the issue?
Thanks!
Hi @Aaron_Turner,
I just checked the status of your ticket and I see that it is still pending review by QA.
I pinged QA again and they will attempt to reproduce the behavior and file a ticket, but as I mentioned above, I can’t quite specify when this ticket will reach their queue.
How has your Roon experience been like except for this issue? Have you found Roon to meet your needs? Are you ready to make the switch or is this issue preventing you from purchasing a license?
Well this bug prevents me from streaming audio probably 90% of the time so I really haven’t been able to effectively evaluate Roon for my needs. At this point, I really can’t see purchasing a license.
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.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.