Nucleus+ attempting to connect repeatedly to phantom IP address

Support Nucleus Support
1

Roon Server Machine

image

Networking Gear & Setup Details

1 x FortiGate-90G 8 x GE RJ45 ports, 2 x 10GE RJ45/SFP+ shared media WAN ports.

1 x Ubiquiti USW-Pro-Max-48- PoE UniFi Switch Pro Max 48 PoE

1 x Ubiquiti USW-Pro-Max-48 UniFi Switch Pro Max 48

5 x Ubiquiti U7-Pro-Max-US UniFi AP 7 Pro Max US

2 x Ubiquiti UACC-DAC-SFP10-0.5M 0.5m UniFi SFP+ Direct Attach Cable
Nucleus+ connected directly to switch via wired connection in rack.

Connected Audio Devices

All wired connections to Bluesound Node 2i, Trinnov Amethyst and Trinnov Altitude.

Description of Issue

Just updated my network equipment to what is listed above. When checking network traffic, my installer noticed the following:
There are a bunch of blocked connections from the Nucleus, it’s trying to talk to “xx.xx.xx.xxx”, which is an IP address in the infrastructure zone, so it’s being blocked. More interesting is that IP address isn’t currently in use, nor was it used by the previous network hardware, so no idea who it thinks it’s trying to communicate with?
When I first installed my Nucleus I was not aware that Roon could not cross vlans, so it is possible that the initial setup included a backup or other device in another vlan. But I have no idea why the Nucleus would still be attempting to connect to an unknown device in my infrastructure vlan.
Any advice on how to troubleshoot?

2

Hi @Kurvenal,

Fully reset the database and see this changes the behavior:

  • Create a Backup of your current Roon Database
  • Stop RoonServer from running in Nucleus’s WebUI
  • Navigate to your Nucleus’ Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old” and “RAATServer” folder to “RAATServer_old”
  • Reinstall RoonOS from the WebUI**
  • Restart the RoonServer in the WebUI to generate a new Database
  • On the Roon controllers, press “Use another Roon Server” and connect to the new database
  • Restore the Backup
4

Hello,

About 10 days ago I reset the database. It looked like the mystery connection attempts had already stopped the day before for no apparent reason. A couple of days ago I reconnected my 2N IP Solo SIP doorbell intercom after disconnecting it while I was having some work done on my front door. Now it looks like my Nucleus is trying to connect to my doorbell, and my firewall is blocking the connections. This seems like unusual behavior to put it mildly. Any more suggestions?

5

Hi @Kurvenal,

Both the doorbell and RoonServer are configured for port forwarding via UPnP. They use the port forwarding component of the UPnP stack. RoonServer and the doorbell are discovering each other as active UPnP port forwarding services.

This is expected behavior and an inevitable consequence of this device architecture and network topology.

If you have configured manual rules in your router for accessing ARC via port forwarding, then there’s no consequence here. If you’re relying on autoconfiguration for port forwarding in Roon, you might experience conflicts if the Nucleus+ attempts to connect to the wrong UPnP service.