Post-upgrade audio routing issue with KEF speakers and ARC connection failure (ref#FJJ8G2)

Support
22

Im afraid I have no idea how to disable a firewall or even if I have one. And I am now away and won’t be back until Friday.

23

Hey @Jeff_McCord,

No problem! We’ll leave the thread open so you can come back whenever you’re able to. Here are some steps to test out temporarily disabling your firewall as I mentioned above:

Open System Settings:

  • On macOS Ventura or later: Go to Apple menu > System Settings > Network > Firewall.
  • On earlier versions: Go to Apple menu > System Preferences > Security & Privacy > Firewall.
  • Disable the Firewall:
  • In Ventura or later, toggle Firewall to Off.
  • In older versions:
    • Click the lock icon in the lower-left corner and enter your password.
    • Click Turn Off Firewall.

Reboot your Mac, and let me know if you still run into issues. :+1:

24

Firewall is already tuned off.

25

By repeatedly toggling off an on the Roon and Roon Server switches under System Sttings>Privacy & Security>Local Network, my KEF LS50’s (which are connected via ethernet) have now appeared. My KEF LS60s, which are not connected via ethernet, but were showing up and connecting fine before all this, are still not showing up.

26

Is anyone still helping me??

28

Hey @Jeff_McCord,

Thanks for the follow-up! From a recent diganostic report, we can see the LS60s are recognized within Roon, but fail to connect, showing:

Warn: [raat_ll/client] [KEF LS60 Wireless @ 192.168.7.252:40439] failed to connect(0) No route to host

Based on the log snippet, the repeated “No route to host” errors strongly suggest a network-level issue is preventing Roon from reaching the KEF speakers. This kind of error usually points to one of the following:

– The KEF LS60 or LS50 units may be powered off, in standby, or not connected to the network.

– The IPs listed (192.168.7.252, 192.168.7.27) might be outdated if the speakers were assigned new addresses via DHCP.

– The Roon Core and the KEF speakers may be on different VLANs, subnets, or Wi-Fi isolation settings that prevent communication.

– A router configuration or firewall could be preventing traffic from Roon Core to the speakers on the required port (40439 / 40795).

– Especially for wireless speakers, momentary drops or slow handshakes could cause the Roon Core to temporarily lose access.

Here are a few next steps to try in troubleshooting:

  • Power cycle the KEF speakers and confirm they’re online and connected to the same network.
  • Ping or access the speaker IPs (192.168.7.252 and .27) from the Roon Core machine to confirm network visibility.
  • Use your router’s admin page to check current IP assignments — the KEF devices may have been assigned different IPs.
  • Consider setting static IPs for the KEF devices in your router to avoid future DHCP changes.
  • If on Wi-Fi, try temporarily connecting the KEF speakers via Ethernet to test stability.
  • Check router for client isolation or VLAN settings that could block local device communication.

Thank you!

1 Like