IPv6 failing for Roon ARC test with ETIMEDOUT error (ref#QJTQ4I)

Support ARC: Port Forwarding Help
1

Network Setup

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

ARC Status

· ARC is *Not Ready*

Roon Error Code

· The ARC settings page says "Not Ready," but I can still connect to ARC via cellular data. I'm having another problem.

Describe the issue

IPv6 is failing again, Roon ARC test is failing with ETIMEDOUT, undefined, undefined, undefined... All other IPv6 services are working fine. Roon works inside the home but Roon ARC cannot connect.

Describe your network setup

I'm on Starlink and you have many copies of my configuration. I use the Starlink router in bypass mode with a CAT6 connection to an ASUS RT-AX3000 router. Roon Server is on an NUC10i7FNH1 using the standard ROCK install.

Let me know if you need a copy of the error from Roon ARC, I have no idea if this new support system has public access or is private.

2

{
“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”:“98.hhh.iii.jjj”,“actual_external_ipv6”:“2605:aaa:bbb:ccc:ddd:eee:fff:ggg”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

3

Should have added that I have an IPv6 pinhole open for the TCP port identified by Roon ARC and port-check verifies that port is available externally…

4

One last thing, Avast is reporting that Raatserver.exe is infected with a virus after installing another update that appeared.

I’m now getting this from Roon ARC test:

{
“ipv6_connectivity”: {“status”:“NetworkTimeout”,“status_code”:998,“error”:“”},
“external_ip”: {“actual_external_ip”:“null”,“actual_external_ipv6”:“2605:aaa:bbb:ccc:ddd:eee:fff:ggg”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

5

Now it’s back to this error:

{
“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”:“98.hhh.iii.jjj”,“actual_external_ipv6”:“2605:aaa:bbb:ccc:ddd:eee:fff:ggg”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

Btw, I haven’t changed a thing since IPv6 was working for me.

6

Roon ARC has stopped working over IPv6. I’ve filed a report but have received no response.

8

Hi @Dean_Kimball,

We’ll activate diagnostics and take a look. In the meantime, I’d re-verify that you’ve added all of the Roon executables to any security apparatus on your Windows machine.

Both the diagnostic messages above indicate a network timeout - the upstream server never responded to RoonServer’s ping through the indicated port. In one case, this seems to occur via the IPv4 pathway. In another instance, there’s no external IPv4 available.

If Avast is flagging another Roon process, then it’s possible it’s interfering with RoonServer here.

Alternatively, RoonServer might be mishandling dual stack - we’ll investigate logs and see what we can find.

Thanks for the report - we’ll get this working together one way or another soon.

9

Hi Connor,

Yes, that is very strange how the error response changed but I can’t explain why other than having rebooted my router to make sure it wasn’t in some odd state. These changes happened when I hit the reload button in the top-right corner of the Roon ARC test well after the router had restarted but that may have been related. However I can verify the following:

  1. I have an active IPv6 address assigned to the ROCK-based Roon Server running on my NUC.
  2. I have an port open for this IPv6 address in the router firewall for the port indicated on the Roon ARC test page.
  3. Roon Server, Roon and Roon ARC are all updated to the latest available early release versions.
  4. Other than updating my Roon systems when new releases become available I have not made any other changes since things were working for Starlink IPv6 and Starlink has not changed my IP addresses.

Thank you for looking into this.

Dean

10

Why was this moved to port forwarding help? As I explained, I’m on IPv6 which does NOT require port forwarding.

11

I believe it’s due to being related to ARC. Roon does not have a dedicated ARC support section, so regardless of whether it is a port forwarding, IPv6, etc. issue, most or all ARC support questions are categorized here.

13

Thanks, you’re probably right.

1 Like
14

Hi Connor, this is a bit late but I just reread your post and want to make sure you understand that Windows isn’t involved in this. My Roon Server is on ROCK installed on a NUC10 as the only OS. Roon ARC is installed on Android Auto.

For my PC’s I run the standard Windows Roon Client but those are working fine…

15

Hey Connor, I figured it out. There is something weird going on with the IPv6 port on the Roon ARC test. No matter what I do the Roon ARC test it always fails on when I set the IPv6 Firewall port to 55002 TCP so I set my IPv6 firewall to 55002 for both TCP/UDP and now it works. Do you have any idea why? Your documentation all says TCP…

Dean

16

Hi Connor,

Can you please let me know if the IPv6 firewall issue is addressed? I need to know if IPv6 needs a pinhole for the Roon ARC port for both TCP and UDP or if this is a bug. If it’s a bug I would like to know when I can remove UDP access to the 55xxx Roon ARC port in my firewall. If it’s not a bug I would suggest updating your documentation so others using IPv6 know that both TCP and UDP are required.

Thanks,

Dean

17

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