After update No port forwarding 5G mobile

[Marc_Kouwenhoven]

Roon Core Machine

Core = Mac mini 2012 fully updated.

Networking Gear & Setup Details

Deco 60 router

1. Who is your internet service provider?
   T-Mobile

2. Please list the make and model of your modem and router?
   TP-Link DECO x60

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

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

Connected Audio Devices

Auralic streamer?DAC via ethernet

Description of Issue -

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

Aftre the latest update the port forwarding fails. Via WIFI in the network its alricht but RoonARC cannot find the core:

{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“163.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“192.168.1.64”},
“status”: “status”: MultipleNatFound
,
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.68.1”,“found_upnp”:true}
}

Roon-core IP and port are right (in the router and in Roon)

[SvenM]

Seems strange that this would be caused by the latest Roon update. The error message suggests this is a case of Multiple NAT.

ARC Port Forwarding

[Marc_Kouwenhoven]

The modem Nokia XS-2426G-B) is in bridge-modus. The router is in wifi-router modus. I have never had a problem before this last update. Is it not possible that something with the update went wrong? There are more of the same issues so it seems…

[SvenM]

@Marc_Kouwenhoven

Is it not possible that something with the update went wrong?

It’s always possible that something went wrong with the update. It’s also a normal reaction to think that the update is caused the issue when this is the last thing that was changed prior to noticing the problem.

I only pointed out what the error message was saying. From this it seems that your router (TP LINK) has an “external” ip of 192.168.1.64 while your true external ip address is reported as 163.aaa.bbb.ccc (not fully disclosed for privacy and security). This suggests that bridge mode is not active.

For all you know T-Mobile pushed an update to their router as a result of which bridge mode is not longer enabled.

[connor]

Hello @Marc_Kouwenhoven,

While the update did contain connectivity changes and a reduction in the number of erroneous popups related to connectivity, we didn’t push any updates that would have affected the port test. We’ll investigate this case thoroughly to be sure.

That said - @SvenM’s above comment is correct in that no change within Roon’s capacity could change your reported external IP address. Every indication suggests a settings reset or ISP update in your T-Mobile-provided router or Deco x60 is responsible for the double-NAT layer. I suspect both routers are active here, and the gateway is no longer bridged. Please verify and we’ll proceed from there. Thank you!

[Toine_Frijters]

I have the same problem, after the latest update Roon 2.2020. No connection possible.
UPNP as port forwarding.