Thank you for the clarification. Since you have a separate provider from T-Mobile (USA), I’ve split your post into a dedicated thread to provide more direct and precise troubleshooting steps.
First off, do you have the latest firmware on the Linksys-based mesh setup? Since outdated UPnP protocols can present security risks, many routers will shadow-disable UPnP by default if the router firmware and security settings aren’t up-to-date. For due diligence, it’s worth restarting the router and both upstream/downstream network hardware to kick any automatic updates.
Scanning through some previous posts by users with Airband UK, as well as external troubleshooting forums for fibre networks, there’s strong evidence that your ISP has in fact implemented carrier-grade NAT on your account. To open a new front in our efforts, it’s likely worth reaching out to your provider to inquire about a dedicated public IP address for your account. The vast majority of users stranded behind carrier-grade NAT have resolved their situation and successfully configured port forwarding by this method, although it occasionally requires a price adjustment on your ISP account.
Additional steps to try:
You can set a manual port forwarding rule in your router’s web administration page. Usually, there is a dedicated port forwarding section where you can specify a static local IP address and destination port, which would match the settings you’ve configured in Roon → Settings → ARC.
Toggle UPnP on/off in the access points and main router. Sometimes, you simply need to jumpstart the UPnP stack for the Core to pick it up.
We’ll be standing by for your response. Thank you!
We’re very sorry to hear that port forwarding is still an obstacle to you enjoying Roon outside the home.
Are there any new diagnostic messages listed in Roon → Settings → ARC after updating to the latest version of Roon and ARC today? @Michael_Evans1, do you have any diagnostics visible in Settings → ARC? Please paste them below as well if so. While it’s likely you’re both encountering Airband’s CG-NAT, we do want to investigate the possibility that we could troubleshoot your setup without involving the ISP, and there’s a chance at least one of the issues here is resolvable.
I’ve done a little digging, and it does appear that Airband has offered customers static or dedicated external IP addresses in the past, but only after the customer applies significant pressure. See the Twitter exchange, for example https://twitter.com/ukairband/status/1318503992054419456
In the meantime, Roon’s developers continue to make progress on connectivity mechanisms that will democratize access to ARC even with restrictive internet service providers. Additionally, we’re shoring up our support team resources to more precisely diagnose and assist port forwarding cases moving forward. Hopefully, this issue won’t persist much longer.