ARC: with asus lyra

[Anders_Borres]

Rock on NUC10i5FNH

Networking Gear & Setup Details

1. Who is your internet service provider?
   Bahnhof

2. Please list the make and model of your modem and router?
   Tilgin HG2381 in bridge mode

3. Do you have any additional network hardware, like additional routers or managed switches?
   Asus Lyra mesh network

4. Does your network have any VPNs, proxy servers, or enterprise-grade security?
   No

Connected Audio Devices

Bluesound node
Sonos port
Sonos one
Sonos amp - old version
Sonos play:3 - old version
Sonos play:5 - old version
Sonos/IKEA symfonisk

Description of Issue -

What is the exact port forwarding error message you see in the Roon Settings → ARC tab?

no contact with Roon Rock from the arc app when outside home wi-fi.

I’ve been in contact with the internet provider and they say that they now provide mi with at public IP. I’ve turned on UPnP and have registered what I believe to be the correct IP and port as port forwarding. I use computers on a daily basis.

diagnostic data for roon support:
{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“82.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“100.66.129.150”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.72.1”,“found_upnp”:true}
}

Best regards
Anders

[Geoff_Coupe]

The error message is saying that you have a multiple NAT situation, and I see two external IP address ranges showing: 82.x.x.x and 100.x.x.x.

This would seem to indicate that the issue lies within your ISP’s control. I would contact them and ask why you appear to have two external IP addresses…

[Anders_Borres]

Thanks for the support. I contacted the ISP but from there end the could only see the 82.x.x.x address. The 100.x.x.x address should be history. But I can still se it in the roon support diagnostics:

{

“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},

“external_ip”: {“actual_external_ip”:“82.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“100.66.129.150”},

“status”: “status”: MultipleNatFound

,

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

“upnp_autoconfig”: {“server_ip”:“192.168.72.1”,“found_upnp”:true}

}

I’ve restarted both the fiber router, the router that acts as a bridge, the asus lyra mesh and the roon rock.

Best regards

Anders

[connor]

Hi @Anders_Borres,

Roon is still detecting a second layer of address translation between the Core and ARC. This address is in the private IP address range often used by ISPs for CG-NAT, but could also be a private network within your LAN created by a second router you still have active.

More specifically, there are a few possibilities to investigate:

1. the router to which Roon is connected is still advertising this address to the Core and/or other connected devices due to cached settings (unlikely).
2. your ISP is still employing carrier-grade network address translation upstream of the address they’ve supplied to you.
3. you have a second router still active on this network, or the ethernet port to which you’ve connected your ROCK is managed separately within the same router (possible with this many router-capable units in the setup)
4. you have a VPN active.

How is your Core connected to the internet? You mentioned a fiber router, a bridged router, and your Asus setup, but I only see the Tilgin and the Asus unit listed specifically. Are you able to diagram your network more precisely like so?
Gateway (model) → Bridged Router (model) → Mesh router (model) —> Core

Thank you! We’ll sort out the blockage before long.