Router is Linksys MX4200 with a BT mesh network. NUC with Roon server is connected via cable to a bridge unit connected to the Linksys. I use the BT mesh to access roon app.
Port forwarding rule in linksys app Rule name - Desktop name External & internal port - 55000 Device Ip - 192.168.1.25 Protocol - UDP & TCP
Web access on router Advanced routing - NAT enabled Admin - UPnP enabled
Port in Roon app is also 55000 Thanks
Describe your network setup
Router is Linksys MX4200 with a BT mesh network. NUC with Roon server is connected via cable to a bridge unit connected to the Linksys. I use the BT mesh to access roon app
The ISP router configured to manage a 10.8.14.0/24 subnet (or a larger subnet - anything up to 10.0.0.0/8 is possible).
A second router connected to the one above (and issued with a WAN ip address of 10.8.14.232) which is configured to manage a 192.168.1.0/24 subnet. Your Roon Server (192.168.1.25) is connected to this second router.
This is the immediate cause of the MultipleNatFound status message in the quoted diagnostic data text.
Does the BT mesh include a router (BT Home HUB)? If it does, then this is likely the cause of the double NAT.
There are a number of ways that you can work around this:
You can eliminate the double NAT by either:
1.1. Configuring the Router connected to the ISP connection point to put it into bridge mode (or modem only mode). Depending upon the nature of your ISP connection, it may even be possible to remove this router completely.
1.2 Configuring the second router to be an access point only so that it offers WiFi but does not perform router functions (and thus no NAT)
Configure double port forwarding by:
2.1. Configure the Router connected to the ISP connection point to forward TCP connections on port 55000 to the WAN ip address of your second router (the one the Roon Server connects to - 10.8.14.232). You will not be able to use uPnP to do this.
2.2 Configure the second router to use a manual port forward (uPnP will not work) to forward TCP connections on port 55000 to the ip address of your roon server (192.168.1.25).
Note: Whenever configuring a manual port forwarding rule on a router, it is a good idea to also configure, on the same router, a DHCP port reservation for the destination device so that is is always issued with the same ip address. This saves having to modify port forwarding rules later.
As an alternative to all of these, you may be able to use Tailscale to setup a VPN tunnel between your Roon Server and your mobile. Instructions on how to do this can be found at:
If, on your Roon Server NUC, you use ROCK installed using UEFI boot, a Linux installation or even a Windows installation, then you will be able to install Tailscale directly on the Roon Server using one of the how to articles linked to from the above article.
However, if you use a ROCK installation using BIOS Boot (RoonOS build number does not update past 259) then the ROCK installation does not support the installation of Tailscale. It is still possible to use Tailscale but but the installation and configuration is more complicated and involves a second compjuter (possibly a Raspberry Pi or similar) running Tailscale configured as a subnet router. A description of Tailscale Subnet Router operation and configuration can be found at:
If using Tailscale (either method) then you will still see the ‘NotReady’ message and the diagnostic text in the Roon → Settings → Roon ARC page - but it will be irrelevant.
You’ll need to follow the steps @Wade_Oram helpfully shared above to either:
configure port forwarding around the double-NAT layer imposed by this two-router setup
or
Install Tailscale on your phone and RoonServer Windows machine to bypass port forwarding entirely.
We often recommend the latter option for more complex home networks, since ISPs can change port reservations or impose CG-NAT and break a manually-configured setup.
Hi. Thank you both for the replies. I tried putting my router to bridge mood but unfortunately that resulted in me losing all Internet and took a out and hour to get sorted with help from my ISP. After speaking to them I am getting a new router and same brand mesh system this week. I will revisit this then but it looks like the installing of the software mentioned is going to be the way to go.