Linn Klimax zone unavailable after successful operation on Nucleus (ref#VS41F9)

Support
1

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Is your RoonServer machine running MacOS 15 Sequoia or above?

· I still can't see my endpoints as available Zones.

Is the affected network Zone connected with Ethernet or WiFi?

· Ethernet

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· Approximately 10:15 am, US PDT when I tried to use system

What are the make and model of the affected audio device(s) and the connection type?

· repetitive issues, not going to pull this info together beyond above info

Describe the issue

Ran Roon successfully for a week or so, with a laptop running Tahoe 26.2 managing network (Roon server in Ethernet connected Nucleus, and audio system's not available again (Linn Klimax, ethernet connected) ... only zone I use/care about ... previous ticket (same issue under Sequoia 15.7.3) was just closed. No restart or power outage ... zone available last night, but not this morning). Too very frustrating ... audio system literally being held hostage by this black box!

Describe your network setup

sere above. Nucleus and Roon ready device on same ethernet wired network

2

Hi @James_Lewis2,

Thank you for reaching back out and we’re certainly sorry to hear that the device discovery issues have returned.

Let’s summarize what we can tell about the connection status to the Linn Klimax, based on diagnostics and what we’ve learned from the previous thread:

  1. Line-of-sight between Roon and the Linn Klimax is intermittent. We can see the Klimax visible in Roon diagnostics as of this writing, but the device was not listed in Roon Settings → Audio just a few hours earlier.

  2. You’ve already ruled out firewalls or network security. Reviewing your previous thread, it sounds like you’ve already toggled local network permissions for Roon in MacOS and performed due diligence on the network connection for the Mac itself.

Taken together, these points suggest that the network pathway between the Linn Klimax and Roon is the most likely failure point. Specifically, the device discovery announcements for Songcast Direct aren’t always reaching the Nucleus from the Klimax. Songcast Direct traffic(Linn’s proprietary protocol) relies on UDP broadcast, which certain network switches and mesh nodes will filter out in an overzealous attempt to regulate network traffic.

We hope to avoid embroiling you in finicky network settings tests, but there’s a high likelihood of resolving the issue if you can provide this specific information to our team:

  1. the make/model of router or switch to which you’ve wired the Nucleus

  2. the make/model of router or switch to which you’ve wired the Linn Klimax

  3. whether 1 and 2 above are the same piece of equipment.

Given that information, we can possibly advise on the right combination of multicast settings to help optimize this network for Roon. It’s not normal at all for this speaker to disappear from the network and we can likely resolve this once and for all.

We’ll watch for your response.

1 Like
3

Gosh, Connor, thank you for such a thorough, technical reply, and forgive me for not supplying that info in my request, since it is key. I’m disabled, and was not eager to pull the system apart to get models, and serial nos. as requested in the basic support request form … but I think I can manage what your asking for here …
the router, which is the network gateway is an Eero 6+

It, the Nucleus and the Klimax are connected through a basic Ethernet switch, which is not clearly identified by make/ model, it can be seen at: Amazon.com: 16 Port Gigabit Switch, Easy Smart Managed Ethernet Switch, Network Hub, Ethernet Splitter, Plug & Play, Fanless Metal Design, VLAN, Qos, Desktop or Wall Mount : Electronics

The devil is that the system will eventually settle down, usually, in 12 - 24 hours (about 6 hours today, see following), and, in fact, is behaving now, as the Klimax showed up as a zone sometime in the last hour or so. This intermittent success led me to believe that the network was sound, and I had a local tech come by to see if it looked good, though he wasn’t addressing the ikind of ssues you’ve identified. Also, if relevant, while Roon was unable to “see” the Klimax earlier today, the Klimax itself said it was connected to Roon on its front panel display, FWTW.
I hope the above is adequate info for your purposes.

Please bear in mind that previously, under Sequoia, Roon server itself, in the connected Nucleus would also be unavailable intermittently, not just the Klimax zone. At least the Roon server has been available today, under Tahoe, even while the Klimax was unavailable as a zone.

Also, I spent some time today with Apple support, since network issues are widely reported for Sequoia. The reps I spoke to disclaimed any knowledge of network issues with OS, even as I showed them the reports. Bottom line, all they suggested was reporting to Product Feedback - Apple, which I did this afternoon. Of course it was during those phone calls that things settled down, and the Klimax became plainly available.
Granted, my knowledge is limited, and given the complexities you identify, my assumption these basic components would suffice may be naive, even though it is a wired setup to a Roon ready device like the Klimax, which does work fine sometimes, just erratically, seemingly randomly.
I’d, of course, be delighted to implement any necessary changes in connection hardware or settings, as you may suggest.

Thank you for your kind attention and help.
I’m trying to learn what I need to have this all work (Roon seems to be a steep learning curve), and feel apologetic for my vexed tone … but it’s not been as easy or clear path.

Let me know if further info is needed. This would be great to resolve.
I greatly appreciate the help,

Jim

2 Likes
4

Hi @James_Lewis2,

Thank you for your response. These finicky network issues are immensely frustrating, and you have my full empathy and understanding.

At its core, this is a device discovery issue caused by how the managed components in your setup handle multicast traffic. The culprit could be either the Eero router or the Goalake 16-port managed switch, so we’ll troubleshoot both, starting step by step.

Let’s begin with the managed switch, since this particular model includes QoS and multicast-handling features that are known to interfere with Roon.

As an initial test, try bypassing the switch entirely by connecting both the Linn and the Nucleus directly to Eero mesh nodes, or even to the same Eero router, if your physical setup allows.

If rewiring to bypass the switch isn’t feasible, the next step is to access the Goalake switch’s management interface. This is often done through a dedicated mobile app. The switch itself should include instructions on how to access its administration page or app, but let us know if you need help locating it.

Once you’re in the switch settings, look for options related to QoS and IGMP snooping and disable them. These settings are often found under a VLAN or similar configuration section. Also make sure that:

  1. All ports are untagged on VLAN 1
  2. There is no port-based VLAN separation
  3. No guest or isolation VLANs are configured
After making these changes, reboot both the Nucleus and the Linn Klimax and check whether the issue improves.

We’ll watch for your response and work from there. We’re happy to clarify any of the technical details above as necessary. Thank you!

1 Like
5

Hi Connor,

It’s very kind of you to have gotten back to me with such a thoughtful overview of what may be creating my problems. Based on yesterday’s message, I had myself concluded it must be the switch that was the culprit, and was in the process of investigating a replacement when today’s message arrived. But I’ve cancelled the order(s) I made, because I’m not even sure what to select: is an unmanaged switch best for Multicast? … because all the managed switches seem to include QoS and IGMP support, and possible VLAN settings all of which need to be properly disabled?

Sooo, after I read today’s message, I dove in. After I figured out how to find its dynamically designated address, I managed to login to the switch’s administrative interface. Unfortunately, trying to implement your instructions was for me like translating one foreign language into another. And while I think I confirmed that DHCP snooping was fully disabled, there was nothing I found clearly designated IGMP, so I just leaned towards confirming anything that sounded like it either monitored or managed traffic was disabled (hence the above question as to whether an unmanaged switch would be the best replacement in this Multicast environment, if necessary.

Nor could I find anything directly addressing your items 1, 2 , or 3 re: VLAN (tagging, separation, or guest/isolation). So, as I said, I simply erred on the side of making sure any monitoring or management was disabled. Since I didn’t really know what I was doing, I was glad I didn’t have to apply any changes, as existing settings seemed to conform at least to the spirit of what you were directing, even if not explicitly in your terms.

So I changed nothing, and rebooted both the router and the Nucleus. I probably rebooted the Nucleus a half dozen times, because its power button does not indicate when its on … occasionally a quick flash or two of dim light will happen, but I never know if that’s indicating shutdown or restart :frowning: So I go by whether the orange light on the power button side of the ethernet connection is steadily on (is that correct?)

Eventually I did succeed in getting the Nucleus rebooted, because, I’ve been happily surprised by both the Roon Server and the Klimax being seen, and some Mozart calms my nerves as I work on this message. (Oh that’s right, I forgot to mention that I’ve been waiting on Roon Server all day, even though first thing this morning everything was OK … it disappeared as I walked over to try and. get into the switch.)

So, as yesterday, the afternoon finds the system working again. (If you wanted a time for the server being found, in addition to the Klimax, that was a bit after 3pm, US PDT, I’d guess … I was just delighted and surprised, and was more eager to see if everything actually worked, rather than checking the time … but I’m pretty close I imagine.

The thing is, I didn’t change any setting in the switch … just rebooted the router and Nucleus, which I’ve often tried to no avail in the past, though that was with my now-retired iMac Pro (which only updates to Sequoia so I had assumed was subject to the connectivity issues you’re aware of and working on. As Tahoe was said to be less obtuse, I’m running everything on a laptop under 26.2 now. Unfortunately the same problems have regularly occurred: waiting on server or Klimax zone unavailable.

But it’s running now, so maybe rebooting will work under Tahoe after all, notwithstanding today’s utter crash. Time will tell …

  1. Do you recommend my replacing this switch for better quality? This was a replacement of a Netgear unmanaged switch I thought might have contributed to my issues, as it was a very basic plastic consumer product. Not sure if this Goalake is any better … (just as an aside, their 7/24 help email address does not seem to exist anymore.) So I’m pretty set on replacement, and just need any guidance you can offer, esp. managed vs. unmanaged.
  2. Anything else to do at this point, besides enjoy these periods of success? And is it the case that the Nucleus (it’s a Rev B) is on when the orange light to the power button side of the ethernet connection is on, stably? (It really is a nuisance to be in the dark about the Nucleus’s status, since I’ve needed to try restarting it so often. One day, I’ll hopefully not need to do that, and can lay the Nucleus down and intended. I’ve needed to leave it standing on itsxside, so the power button is accessible/visible.)

As I said at the outset, I’m really grateful for your effort in formulating an overview of my problem, and phrasing it in a way that enabled me to further educate myself, and find my way as outlined above: gain a wee understanding of the network issues involved in even what I thought was a pretty direct and simple setup.

So thank you very much for your effort, and Vadim’s before you. I’d still like your help with replacing this switch, if there’s any chance it is the weak point, but I’m going to keep[ keeping a positive outlook, learning, and hoping to stop bothering y’all with such persistent and disheartening issues. I’m fully committed to getting this behind me in 2026! But, as note above, Time will tell :slightly_smiling_face:

Very best to you,

Jim

1 Like
6

Hey @James_Lewis2,

Thank you so much for such a detailed follow-up. Along side both @vadim and @connor I am quite confident we can get you back up and running smoothly at all times!

Apologies if this has already been tried- but can you fully remove the switch from your network chain temporarily? See if you can get the Linn and Nucleus with a direct ethernet connection to your router - maybe double check the ports to ensure the routers through-put is the same across all ports.

Let me know if this is something you’d be able to try, thanks Jim!

7

Hi Benjamin,

Yep, @Connor suggested that, if feasible, in the message preceding your own:

And when the persistent issues of Roon clients “waiting” interminably and unsuccessfully for the Roon Server first began persistently arising, my first thought was to connect the Nucleus directly to the router, since that is where the server resides. But it’s not an option, nor was Connor’s suggestion to connect to mesh nodes, for reasons I won’t bother with.

I am a bit mystified that you bothered to pull a quote from my message, while ignoring the questions I had reiterated. Item 1:

And immediately following your quote:

The first question I did find addressed in the forum, so I’m going to replace the switch, if malfunctions continue, with an unmanaged Netgear solution that was reported to work with Linn gear.

I acknowledge the second question sounds ridiculous, but in the context of Roon seeming to need constant rebooting, I assure you it is not. And the Nucleus manual seemed to contradict my hopeful theory … so any guidance on how to discern when my Nucleus rev B is on would be very appreciated, since the power button does not disclose its state, as promised.

Even though I changed nothing in the switch, Roon’s been stable now for almost 48 hours, so I think we’ve done what we can for now (fingers crossed). Before closing this, though, please help with this second question about the power status of the Nucleus rev B. Or perhaps @Connor or @vadim might revisit?

I’m really grateful for the direct attention and support. From my minor hardware issue, to consistent inabilities to use my stereo, Roon’s been a very troubled experience for me. So accept my apologies for sounding grouchy in some communiques, like referring to it as a literal “black box.” As I’ve expressed several times recently, to @vadim and @Connor both, and now to you, I value the thoughtfulness and seriousness of your consideration of my problems, even compassion, so good on ya’ … I see light at the end of this tunnel!
Very best wishes,
Jim

PS And, as I’ve acknowledged above, and wish to reiterate in closing, when things got really bad again this year, I think it was the Sequoia issue driving my problems, so my ire is mostly with Apple now. I’m actually on the verge of getting a Windows laptop, since so many successful Roon installations are Windows based (truly words I never thought I’d be ever writing, as I’ve been an evangelist for both the II and Macintosh since the early 80’s), but it’s not just the Sequoia issue that showed up … when I first tried to back up with a network attached drive, OS would not allow, because that functionality had been based on routines they had improperly “borrowed”, and apparently had not gotten around to fixing with code of their own ( or at least that’s how it was reported by folks on the forum who know more than me … smd?) Anyway, the more I learn, the more I can appreciate the complexities of getting this system to work in so many hardware configurations and software environments. So I very much appreciate the help, especially when other factors are primary culprits.:slight_smile:

8

Hi @James_Lewis2,

This sounds good - apologies for not including answers to your questions prior. In the ideal situation, we’d be able to set up that temporary, direct connection, therefore bypassing any switch altogether. That said, an unmanaged switch is definitely the way to go here.

This information lives here:

Let me know if the info is clear and if this helps!

Since a few more days have passed, how are things running?

Thanks, Jim! :raising_hands:

1 Like