Thanks for taking the time to write in and share your report! The port forwarding diagnostics you’ve provided suggest there is a redundant layer of network address translation preventing port forwarding. This prevents ARC from recognizing the external IP address of your home network.
The second layer of NAT can either be at the local-network level (commonly as a result of two routers), or at the level of your service provider (called “carrier-grade” NAT, or CG-NAT).
Solution:
If your setup involves an ISP-provided gateway (modem/router combination) and your own third-party router:
In the web administration interface of the ISP-provided gateway (modem/router combination), enable Bridge Mode or equivalent, where the ISP-provided gateway does not have DHCP routing enabled.
Alternatively, if you have already created a manual port forwarding rule in your 3rd-party router, you can add an additional rule to forward the port through the ISP/second router.
If you only have one router in your setup or your modem is already in Bridge mode, please take a look through our list of known router and internet service provider solutions, as other users may have already encountered the same situation: [url=https://community.roonlabs.com/t/routers-and-isps/203656]ISPs and Routers: List of Known Solutions and Workarounds[/url].
You can reach out directly to your service provider to ask if they support port forwarding; this question will often enough to prompt them to explain whether or not the carrier-grade NAT they’ve implemented can function with ARC.
Additional Notes:
The MultipleNAT error is not reported unless UPnP or NATPMP is working. Since these protocols configure port forwarding automatically, once you’ve removed the cause of the MultipleNAT error, port forwarding should automatically configure in Settings -> Roon ARC.
Please see the screen shot for Step 1-This is from Roon App
Step 2- this is from my Eero App
Step 3.1-Eero App, Advanced netwroking
Step 3.3-Eero App, Advanced networking continuation.
I am still getting error and cannot get the Roon Arc working.
This line in your original post indicates that your ISP is using CG-NAT because your router is being assigned an IP address in the range 100.64.0.0 to 100.127.255.255 which is reserved for CG-NAT.
With CG-NAT involved you will be unable to get port forwarding working unless you talk to your ISP to get them to offer a solution (some do, some don’t. Many charge extra for their offered solution).
Alternatively, you may be able to ignore port forwarding and set up Tailscale on your Roon Server and your mobile device(s) to give you a VPN tunnel directly to your Roon Server no matter where you are.
I am checking in Router Advanced setting and it has “DHCP & NAT”. The option I have under that is; Automatic, Manual IP and Bridge. Is this something I can change and make it work.
Thanks
KP
That setting on your router is not the root cause here.
Your diagnostics show this IP:
100.65.xxx.xxx
That range means your ISP is using Carrier-Grade NAT (CG-NAT). This is done on the provider’s side, not on your router, and it prevents port forwarding from working — even if UPnP / NAT-PMP is enabled.
Changing the DHCP & NAT mode on your Eero won’t fix this. The only ways forward are:
Ask your ISP for a public IPv4 address (or CG-NAT opt-out), or
Use a workaround like Tailscale instead of port forwarding.
Once CG-NAT is removed by the ISP, ARC should configure automatically.
Hi,
I will try talking to the ISP provider but not sure what would they say.
Like to know how to work on the Tailscale. Can you please step by step procedure so I can follow it accorndly.
Thanks
KP
The details of installing Tailscale differ with your Roon Server host. The general description can be found here:
Note that this page provides links for different types of Roon Server installation (ROCK/Nucleus, Windows, Mac, Linux) and you must follow the appropriate link to get to the installation instructions for your particular Roon Server.
Also note that, at present, it is not possible to install Tailscale on the original Nucleus and Nucleus Plus models (and some ROCK installations) as they were originally shipped because they employ the old BIOS boot mechanism which is not supported on the versions of RoonOS that support Tailscale.
If you are using ROCK with such an install, it may be possible to re-build your ROCK Roon Server using UEFI boot but you will have to make sure that you have a good, working backup of your Roon Database before you start because the procedure will completely reformat your Roon Server system SSD.
The steps to do this are:
Perform a Roon Database backup if you don’t have a suitable one already
Test the backup (maybe using a temporary Roon Server on a windows or Mac machine) to ensure that it can be used successfully.
Download the Balena Etcher application for your computer and install it
Use Balena Etcher to create a bootable USB stick (or USB disk) using the Roon ROCK installer image downloaded in step 3
Install ROCK as Normal
6.1. Attach a USB keyboard and an HDMI monitor (or TV) to your ROCK Roon Server machine
6.2. Reboot the ROCK Roon Server and, during boot enter the BIOS setup (usually by pressing either the ‘del’ key or the ‘F2’ key).
6.3. In the BIOS setup, change the boot mechanism to UEFI and set the boot device priority to allow booting from USB
6.4. Reboot the NUC using the USB stick created in step 5
6.5. Wait for the installation to complete
6.6. Reboot the NUC into RoonOS (not this will be an old, obsolete version of RoonOS and the Roon Server software)
6.7. Use a Web browser to navigate to the RoonOs WebUI (usually http://Rock or http://Rock.local
6.8. Click on the ‘Reinstall’ button in the WebUI to install the latest version of RoonOS and the latest version of the Roon Server software. After this procedure, the RoonOS version number should be version 2.1 build 271 (at time of writing).
Restore your Roon Database from the backup that you created in step 1 (or tested in step 2).
The alternative is to use another small, cheap, power efficient (since it will need to be left on 24/7 - or ar least be on whenever you want to use ARC) computer (like a Raspberry Pi) and setup Tailscale on that computer as a subnet router. Instructions for that can be found at:
It should also be noted that I have seen a few cases of people on these forums using the ROCK reinstall using UEFI boot procedure detailed above to install the ROCK software on Nucleus and Nucleus Plus devices with UEFI boot so that they will also update to the build 271 of RoonOS and thus support Tailscale. I believe that, once this is done, Roon support can be used to re-instate the Nucleus/Nucleus Plus identity to the device. However, I’m not sure of the extent to which this is a supported option for Nucleus and Nucleus Plus devices and it is, maybe, something that should be carefully considered before undertaking.
Vadim,
If I call the ISP provider and ask them to provide me with the Globally available IP address or perform the port forwarding for me–
What information they need from me.
Thanks
You can reach out directly to your service provider to ask if they support port forwarding; this question will often enough to prompt them to explain whether or not the carrier-grade NAT they’ve implemented can function with ARC.
