· I'm having trouble with Roon ARC
· I can't log into ARC but I can log into Roon
Roon Arc Port forwarding setting
Roon Arc shows port forwarding issues
Not sure how to set the port forwarding correctly
Service Provider: Unifi Malaysia
Modem: FiberHome GPON ONU HG6240A
Wifi Router: Dlink DIR-X3060Z
Can you post a screen shot of what you see when, in the normal roon client (not ARC), you go to Settings → Roon ARC?
If there is any diagnostic text displayed, then copy it to a reply in this thread.
This may help us to understand the issue.
Normal Client normal & green light
I suspect that either you have set up port forwarding for IPv4 connectivity but, when outside your network you are using IPv6 which does not have a firewall rule configured or, more likely, the other way around. You have an IPv6 firewall exception configured but no IPv4 port forwarding configured and you are trying to connect over an IPv4 connection.
I your original post, you showed a screenshot from your router admin pages for port forwarding.
I would start by adding a port forwarding rule there.
Enable: checked
Name: anything you like but I use ‘RoonARC’
Protocol:TCP
WAN start port: 55002
WAN stop port: 55002
LAN host ip address:192.168.1.10 (your Roon Server ip address)
Virtual host port: 55002
Then click “Add”.
I know nothing about ipv6 and see no info on its firewall. Do u think i’ll just set the connection to just ipv4 and it’ll work for roonarc?
You could, as an experiment, try disabling IPv6.
The least intrusive way of doing this would be to do it locally on the Roon Server machine (I don’t think this is possible if you use a RoonOS device (Nucleus, ROCK, MOCK).
If you can’t disable IPv6 on your Roon server, you should be able to disable IPv6 for your whole network in your router settings. On some DLink Routers, it looks like you can’t disable IPv6 but your can set it to apply to the ‘Local Network only’. This would work equally as well.
Once you have IPv6 disabled on your Roon Server, you should be able to click on the refresh button (circled in red in the image below) to update the Roon ARC connectivity status.
With IPv6 disabled, it may give you more information about your IPv4 connectivity.
The only other thing that I can think of is the presence of a firewall on your Roon Server. However, from the host name (“tande-mac-mini”) I’m guessing that your Roon Server is on a Mac Mini. I don’t know anything about firewalls in MacOS so I can’t help further.
Hi @Gary_Tan,
Thanks for writing in to ask about this issue. Try what @Wade_Oram advised and let us know whether or not it resolves your issue.
Hi @Gary_Tan,
TM Unifi is known to have implemented CG-NAT for their IPv4 addresses, although Roon can’t confirm whether that’s universally true for account holders.
If you find you cannot create an end-to-end IPv6 connection via Wade’s helpful instructions, consider installing Tailscale on your server machine and phone as an alternative.
Yes my roon server is on an old mac mini (mid 2011) running on macOS Catalina 10.15.7
I’ve set Ipv6 to ‘Local Network Only’ and the Roon Arc screen shows this:
{
“ipv6_connectivity”: {“status”:“Success”,“status_code”:200,“error”:“”},
“external_ip”: {“actual_external_ip”:“118.kkk.lll.mmm”,“actual_external_ipv6”:“2001:aaa:bbb:ccc:ano:aop:apq:lll”,“router_external_ip”:“100.hhh.iii.jjj”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.1.1”,“found_upnp”:true}
}
Please advise, thank you very much!
OK. This confirms that, when IPv6 was enabled, you had a working IPv6 connection which was why Roon ARC settings reported ready.
However, this latest setting shows that your IPv4 connection is not working because of a ‘MultipleNATFound’ issue.
This is most likely to be the use of CG-NAT that @connor suggested was the issue.
In that case, you can either setup Tailscale as @connor suggested or you can talk to your ISP who may be able to supply a public, probably static, Ip address although they may charge extra for the feature.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
