Roon client on PC intermittently recognizes connected devices (ref#980HLU)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· After not useing roon for several months the client on my pc only shows some devices connectet to pc constantly and some others connectet to pc for a millisecond. What is going on here? I did't change a thing, i updatet to the newest roon client, server says newest version. Firewall on pc is full open privat/public tcp/udp for roon and raat. Any short solution? This is really annoying.

Tell us about your home network

· Roon server connectet to fritzbox via switch

2

Ok, I figured it out. A few weeks ago I had to install a VPN tunnel for office reasons, I had completely forgotten about that. I first deactivated the tunnel, but I had to close Wireguard completely, and now Roon is running smoothly again on this PC. How stupid was that?

3

Hello @Joachim_Koerth,

Glad you figured it out! For future reference, instead of closing WireGuard completely you can exclude local network traffic from the VPN tunnel by adding the following routes to your WireGuard config under AllowedIPs:

64.0.0.0/2, 32.0.0.0/3, 128.0.0.0/3, 16.0.0.0/4, 176.0.0.0/4, 208.0.0.0/4, 0.0.0.0/5, 160.0.0.0/5, 200.0.0.0/5, 12.0.0.0/6, 168.0.0.0/6, 196.0.0.0/6, 8.0.0.0/7, 174.0.0.0/7, 194.0.0.0/7, 11.0.0.0/8, 173.0.0.0/8, 193.0.0.0/8, 172.128.0.0/9, 192.0.0.0/9, 172.64.0.0/10, 192.192.0.0/10, 172.32.0.0/11, 192.128.0.0/11, 172.0.0.0/12, 192.176.0.0/12, 192.160.0.0/13, 192.172.0.0/14, 192.170.0.0/15, 192.169.0.0/16

This replaces 0.0.0.0/0 and excludes RFC1918 private address ranges (192.168.x.x, 172.16-31.x.x, 10.x.x.x) from the tunnel, allowing Roon to discover local devices while keeping your office VPN active.