I don’t know whether or not it is possible to enable UPnP or NAT-PMP with this Internet gateway as the settings menu is extremely basic and doesn’t list anything related to advanced options such as NAT or port forwarding. Please bear in mind that this is a modem, router, and access point combined in a single device which connects to the Internet using T-Mobile’s cellular network in the US.
Unfortunately it may be that TMobile 5G does not provide a routable external IP address. I know that this is true for many cell carriers with traditional WWAN routers. Also in general, it may be simpler to just manually configure port forwarding. That’s what I did with Xfinity Cable and my Untangle FW. Works great!
I just spent an hour on the phone with T mobile. The help desk supervisor ended up telling me that the T-Mobile gateways don’t support port forwarding and basically you can’t set up ARC with their system. We. Will have to wait for a software update or even a hardware upgrade in the future. Until there, stay home…
Thank you both for your replies but I am limited to the hardware I have: Roon nucleus (I can’t configure anything there like VPN) and T-mobile router (where I can’t really see any configuration options either. It is more designed to be plug and play). I’ll try to find those VPN posts but I’m not very hopeful.
Unfortunately, it’s true that the particular IPv4 tunneling implementation used by T-Mobile 5G residential tier accounts doesn’t preserve port assignments, so returns from your mobile device using ARC are filtered out and unable to reach the Core. This will manifest as the frustrating experience you’ve been facing for these last months: endless timeouts in Roon → Settings → ARC, and a “Can’t Find Your Core” screen in ARC outside your local network.
This particular situation is further complicated by T-Mobile’s Arcadyan gateways, which do not support UPnP and do not allow for manual port assignment.
In short, Roon users with your internet setup are stuck without ARC outside the home for the time being. From the team side, we have an urgent and high-priority initiative to allow ARC to function with IPv6 addresses, among other tickets to ease up the obstacles presented by common CG-NAT. We anticipate this will solve many major ISP-level blockages with ARC or otherwise open up supported workarounds. The team will be posting notes in our general tracking thread for ISPs and carrier-grade NAT issues here: ISPs and Routers: List of Known Solutions and Workarounds
Thanks Connor - not good news but this clarifies a lot, and there is hope that eventually this can be addressed.
When posting solutions/workarounds as they become available, please
identify T-mobile in the tile
keep in mind that many of us (including me) are not techies so we need step-by-step dumbed-down instructions like you would teach your mother
and not everyone is using a PC: in my case I am using a nucleus + and an ipad to drive it, so I can’t get in there to tweak things, and I can’t implement a crafty fix designed for PC. Again, I need something simple .
I don’t mean to be demanding with the above, I’m just a computer-ignorant end-user (and music lover) at the mercy of technology (and those who know). Thank you very much indeed for helping people like me. Really appreciated!
We’re continuing to make progress with our efforts to allow for more complete IPv6 compatibility with Roon ARC. Ideally, this would relieve a large swathe of CG-NAT issues trapping users on major networks like T-Mobile. We can’t guarantee it will help every user, but we are working hard to open access to ARC to our full user base.
@AvilleAudio, don’t worry, any solution we come up with will work for RoonOS Core users.