Issue with ARC functionality after switching to new ISP (ref#AH2IO8)

What’s happening?

· I'm having trouble with Roon ARC

What best describes your issue with ARC

· Other

Describe the issue

I switched to a new ISP and now ARC has stopped working

Describe your network setup

100Mbps broadband using mesh network and wired connectivity for some devices including Roon server

Below is the diagnostic data when I tried to connect to ARC

{
"ipv4_connectivity": {"status":"NetworkError","status_code":504,"error":"error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined"},
"external_ip": {"actual_external_ip":"159.ddd.eee.fff","actual_external_ipv6":"null","router_external_ip":"100.aaa.bbb.ccc"},
"status": "status": MultipleNatFound
,
"natpmp_autoconfig": {"server_ip":"192.168.0.1","found_natpmp":true},
"upnp_autoconfig": {"server_ip":"192.168.0.1","found_upnp":true}
}

@Kentaga_Kartadinata, based on your ARC error message, the second IP address (starting with 100.aaa.bbb.ccc) indicates your ISP is using CG-NAT (which shares one public IPv4 address across many subscribers).

Unfortunately, Roon ARC cannot work across a network using CG-NAT. You may be able to request a static IP address from your ISP or set up a Tailscale VPN to make ARC work in this situation.

Information on Roon’s use of Tailsale (which I use) is here:

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.