Hi,
I have similar Problems.
{
“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”:“94.hhh.iii.jjj”,“actual_external_ipv6”:“2a00:aaa:bbb:ccc:ddd:eee:fff:ggg”,“router_external_ip”:“100.kkk.lll.jjj”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.178.1”,“found_upnp”:true}
}
I have a second router (AVM) as Mesh Repeater.
Any step by step Installation Guide would be nice.
Thanks
It looks like your ISP is using CG-NAT because:
- Ip addresses in the 100.64.0.0. to 100.127.255.255 range or usually issued by CG-NAT gateways
- Both the 100.kkk.lll.jjj address and the 94.hhh.iii.jjj address are routable and must, therefor, lie outside of your network.
There is nothing that you ca.n do to resolve this yourself. You will have to talk to your ISP about getting either a static ip address or an ip address from a non-CG-NAT pool in order to be able to support the operation of a internet facing server (The Roon server in your case).
The ip address of your router (192.168.178.1) does not look like a typical ip address for an ISP gateway router. Is this the ip address of your WiFi Mesh router? If so you have 3 levels of NAT activity going on but this one can be resolved yourself. The WiFi mesh router should be configured to be an access point only so that it does not create a separate sub-net and does not provide address translation or DHCP services.
@moderators
Could you move this post to the new ARC Not Connecting to roon thread. I replied at about the same time as the two posts it relates to were split off.
Hello, what kind of router do you have, type FritzBox……
Thanks for your Support. I will contact my ISP to solve tge Problem
Hi @Olaf_Schroder,
Thank you for your post. We’ll keep this thread open until you confirm you’ve heard back from your ISP.
I also suggest you search for the name of your provider in the ARC: Port Forwarding Resources subcategory, as many Fritz!Box users with CG-NAT situations have shared their stories there.
Hi Connor,
I take an alternative way to run ARC and it works fine:
Setup a VPN Tunnel via WireGuard on the fritzbox. Installed WireGuard App. Set in ON and Magic worked.
Simple and clean and no extra fee for the ISP.
Thanks for Support but solving the problem (ip6 vs ip4) native by roon is still needed.