It looks lije you have two routers in your network, one connected to you ISP line creating a 192.168.0.0/24 subnet and another, with your Roon Server attached, creating a 192.168.1.0/24 subnet.
In this scenario uPnP cannot configure both routers. It can only configure the router to which the uPnP client (Roon Server in this case) is connected (Presumably the Linksys MR9600).
In order to get Port forwarding working with your network as it stands, you will have to abandon the use of uPnP and configure a port forwarding rule on both of your routers.
On the router that handles the ISP connection, create a port forwarding rule to forward TCP connections on port 55002 to the WAN side ip address of the second router (192.168.0.15).
On the router to which you Roon Server is connected, create a port forwarding rule to forward TCP connections on port 55002 to the Roon Server ip address(192.168.1.92).
Alternatively, if the router that handles the ISP connection supports it, you could set it to ‘bridge mode’ or ‘modem only mode’ so that it ceases to act like a router (no NAT and no DHCP). If you do this, the uPnP setup on the router to which the Roon Server is connected may start working.
Neither of these solutions will work if your ISP uses CG-NAT. In that case, you will either have to ask your ISP if they can supply a public ip address that supports port forwarding (possibly at extra cost) or you will have to use Tailscale.
If you use a Nucleus, a Nucleus Plus or a ROCK system using RoonOS version 259 that won’t update to the latest (version 270), then you will not be able to setup Tailscale on your Roon Server.
Instead you will have to setup Tailscale as a Subnet Router on another computer that is always on that is connected to the network using a wired connection. It does not have to be a powerful computer. A Raspberry Pi 4 would be good enough.
It depends on the Boot method. ROCK installations using BIOS boot will only update as far as build 259. By contrast, ROCK installations using UEFI boot will update to the latest version of RoonOS whatever that might be (currently build 271).
Roon have suggested that a solution may be comming at some date for the Bios Boot Nucleus devices so such a solution would presumably also apply to BIOS boot ROCK installations. However it is not here yet:
Unfortuantely, if your ROCK install is using Bios Boot, there is no easy way of converting to UEFI boot. If your NUC supports it, you have to change the boot mechanism in the BIOS and then re-install ROCK from scatch (obviously making sure that you have an up to date, and valid, database backup to restore from).
Modern NUCs (I don’t know exactly how modern but it certainly applies to my NUC11) default to UEFI boot so a ROCK install performed recently on up to date hardware will almost certainly install RoonOS build 271 (or at least a version that allows you to use the “reinstall” feature of the RoonOS WebUI to bring the RoonOS and Roon Server installation up to date.
Diagnostics indicate that you’re running UEFI-supported hardware - if you reflash ROCK to this machine, it should install with the latest RoonOS build available.
