Thanks! I pay for a static IP and restarting the computer and power cycling the router always results in the same external IP address, so I’m pretty sure there is a static IP, but I’ll contact my ISP when they’re open and check up with them.
UPNP seems to be working as intended on the router. My Roon computer is on 192.168.0.2 and whatever i change the port to in the Roon Arc Settings gets updated in the port forwarding list on the router. So not sure if manually forwarding ports is necessary. Do I need to also somehow forward a port through the static public ip address (i.e make a rule in the router’s forwarding settings through 147.xxx.yyy.zzz)?
Try creating a manual port forwarding rule in the Sagecom admin settings page. This rule should be TCP format and point to the IP address and port number listed in your Roon Settings → ARC page.
Your initial message mentioned a ConflictinMappingEntry diagnostic, although I don’t see that in the screenshot. That particular message refers to a port mapping conflict; some other software program has reserved the port UPnP has attempted to automatically assign to Roon. The solution is to simply type in a different port (like 55010 instead of 55000) in Settings → ARC.
Let us know if this helps. It’s also worth verifying that Sagecom has actually removed CG-NAT for your account, but it seems you’ve already reached out to them to confirm.
I contacted my ISP and it was true that they hadn’t properly given me a static public IP. (they swapped out my router last week and the static IP got forgotten in the shuffle by then.)
However, it took some more troubleshooting and a few more resets to get Roon ARC connectible. I found a separate issue that was preventing this:
My roon server (running on a mac mini) was connected by both WIFI and Ethernet Cable. In MacOS’ settings, I have prioritized the Ethernet connection, which was at the reserved internal IP of xxx.xxx.0.2, while the WIFI connection was on reserved IP xxx.xxx.0.22.
What’s interesting (and possibly a an error in Roon?) was what in the Roon app, the “Roon Server IP” was the ethernet connection (xxx.xxx.0.2) but in the router’s settings, i could see it was actually forwarding the port to the reserved WIFI address (xxx.xxx.0.22) via UPnP (i didn’t forward the port manually). So I guess the Roon ARC server check was either checking or forwarding the incorrect port?
As soon as I shut off the server’s WIFI and chose a new port (to trigger a new UPnP port forward) the Roon ARC server went to “Ready” and everything is fine.
Excellent work, and thank you for coming back with the full explanation. That is a better write-up than most, and two separate things had to be fixed before it would work.
The first was the one BlackJack spotted from your diagnostics. router_external_ip beginning 100. is carrier-grade NAT address space, which is why the connection test returned 504 and why MultipleNatFound appeared. Your ISP confirming the static IP had been forgotten during the router swap fits that exactly.
The second is your own finding, and it is worth explaining because you are right that it looks odd. Your Mac mini had both Ethernet and Wi-Fi active, on 0.2 and 0.22. Roon reports the address the operating system presents as the primary one, which was your Ethernet interface. The UPnP mapping, though, is created from whichever interface the request actually left by, and that was Wi-Fi. So the router dutifully forwarded the port to 0.22 while Roon was listening on 0.2, and nothing arrived.
With two active interfaces there is no reliable way for Roon to know which one you intend traffic to arrive on, which is why we recommend running Roon Server with a single active network interface, wired for preference. Turning Wi-Fi off, as you did, is exactly the right answer, and changing the port afterwards was the necessary second half of it, since that is what forces a fresh UPnP mapping rather than leaving the stale one in place.
So for anyone who finds this later, the combination that fixed it was: get the static IP genuinely provisioned, disable the second network interface on the Roon Server, then change the ARC port to trigger a new port mapping.
