Roon ARC setup issue with incorrect IP address on MacMini (ref#MUHW5L)

Support
1

Network Setup

· I use my ISP's router alongside a personal router.

ARC Status

· ARC is *Not Ready*

Roon Error Code

· “natpmp_autoconfig”: {“status”:“NotFound”}, “upnp_autoconfig”: {“status”:“NotFound”} }

Have you successfully located and enabled the UPnP or NAT-PMP settings in your router's web UI?

· I've turned UPnP/ NAT-PMP on and ARC won't connect

Select the Diagnostic Keyword or Text String

· Something else

Don't give up yet.

· I'm stuck. I'd like to create a post to ask Roon Community for help.

Describe the issue

Trouble setting up Roon ARC. Roon Server setup on a MacMini, I have UPnP enabled, I have a port forwarding set up to point to the IP address for the MacMini (a static address in the 192.168.1.[] range), but the Roon Server IP listed as my "Listening Port" is given as 10.2.0.2 (outside the ranges that I am aware that my router uses)

Describe your network setup

ISP is Starlink, Starlink modem in bridge mode, with Netgear ORBI 850 as my Router. RoonServer on a MacMini M2 Pro, connected via ethernet to the Router. OS Sequoia 15.4.1

2

Hello @neil.marshall,

Thank you for reaching out to Roon support.

I’ve enabled diagnostics mode for your account, and we can see that you have multiple active physical interfaces and one virtual interface, commonly used for VPN connections.

The active interfaces on your system are en0 (IP: 192.168.1.33) and en1 (IP: 192.168.1.105). Additionally, utun4 (IP: 10.2.0.2) appears to be a virtual network interface associated with a VPN or tunneling connection.

It seems that ARC is getting confused about which interface to prioritize and is defaulting to the VPN interface.

Could you please try disabling the VPN client temporarily and check the behavior again? This should help determine if the VPN is indeed causing the issue.

Let me know if you need further assistance.

3

Thanks. Disabled the VPN, and yes, the IP for the listening port is now correct. The en1 interface was a temporary install before I received the MacMini now setup as en0.

I am still struggling with connecting via ARC, and it is still recording a Not Ready state. Tried to copy the text into the box but failed! For some reason it’s not finding the UPnP config.

4

Hello @neil.marshall ,

Thank you for the update.

Let’s quickly check whether Starlink’s bridge/AP mode is causing the issue:

  1. Bypass the ORBI
  • Connect your MacMini directly to the Starlink Wi-Fi (AP mode) or via Ethernet into the Starlink unit.
  1. Test ARC

  • Restart Roon ARC and see if it turns Ready.

  • If ARC works: the ORBI (double-NAT) is blocking UPnP.

Let me know what you find!

1 Like
5

Hi Vadim

I have tested the Roon after resetting the Starlink device to remove bridge mode and using the Starlink Router as an AP.

Unfortunately, this didn’t work. So that eliminates the double NAT possibility. The troubleshooting code that I got from setting things up direct with the Starlink router are below:

{
“ipv6_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“145.vvv.uuu.aef”,“actual_external_ipv6”:“2a0d:ddd:eee:fff:amn:ano:sss:aop”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

This compares with the diagnostic data from using the Starlink Router in Bridge mode:
{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“79.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

The difference between the two is that with Starlink as the AP, it identifies an “actual_external_ipv6”

The Starlink router is very constrained in terms of the networking settings that you can change (no port forwarding for example), so I’m going to revert to having it in bridge mode.

I hope you can help resolve this (it will be a problem until I can dump Starlink in a few months time as fibre rolls out)!

Neil

6

Hello @neil.marshall,

Thank you for the update.

[quote=“neil.marshall, post:5, topic:298332”] “natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”} [/quote]

As we can see from the output, both UPnP and NAT-PMP are not enabled on the Starlink router, and as you mentioned, there is no option for port forwarding. This confirms that the issue lies with the Starlink router, which is blocking incoming ARC requests.

In this case, we recommend using Tailscale VPN to access your device with ARC without the need for port forwarding.

7

Thanks Vadim

Using Tailscale has helped me get Roon fully operational in my setup, and with RoonARC, out of the house as well.

Thanks for your help.

Neil

8

Hello @neil.marshall,

Thank you for the update!

We are glad that everything is running as expected. Enjoy your music!

9

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