not sure what you mean - all Roon Core and Linn devices are all on same subnet. there are no options to configure LAN segment settings in Settings → Setup that I can see. If Roon Core cam see the Linn DSMs as Airplay, then it should see them as controllable audio devices. I have made no changes to LINN Konfig settings between running on Roon Core 1.8 and 2.0 - all Linn DSMs are set to Roon visible.
At the bottom of the Settings → Setup screen there is a “Subnet for Linn streaming” setting. Not that I have any Linn devices so I can’t experiment with this, but if somehow the subnet configured there is different from the subnet that your Linn devices actually live on then I can imagine that the Roon core has difficulty seeing them.
By the way, the release notes for today’s 1148 does mention that they made some changes for stability’s sake related to some Linn devices; perhaps that change causes you problems.
(Torben - A Dane living in Hamburg - Roon Lifer)
@Jay_Whyatt I have a Linn Selekt DSM Surround and it shows up after the update today:
This bug might be based in RoonOnNas rather than Roon itself (I think RoonOnNAS packages the Linux server, which itself mostly uses the Windows files + Linux dotnet I think), so we are multiple layers of abstraction from the original code.
That said, RoonOnNAS is linked from the Roon website in the same way as other downloads, so while they might not support it themselves they are happy to let us pay for Roon on the basis we should be able to run it on a NAS.
Have any of you folks who are experiencing this issue on a QNAP tried temporarily turning off the device’s firewall? This issue could be related to a network discovery strategy that is being blocked.
It needs to be fixed quickly even if that means reverting the Linn “fix” in the latest Roon build. In the meantime, it might be worth exploring if there’s a configuration change you can make to get it working again.