· If I plug the NucleusPlus into my home network, the Internet will be unavailable on the wifi band. This error occurs with a Synology RouterRT1900ac, TP-Link Archer AX53, TP Link Archer AX73 router. However, it works perfectly with an approx. 15 year old Linksys_wrt120n router, but it is only a 150 Mb/sec router for my Gigabit internet. What could be the error?
Tell us about your home network
· My Hungarian internet provider is Digi-One. The optical internet arrives at the provider's modem, which is connected to the bridge. From there, the Synology RouterRT1900ac's WAN input receives the signal from port 1. The signal goes from LAN port 2 via a 10m cable to an Aqwox Audio devices switch. The TV and all my audio and video equipment receive the network from these.
Thank you for providing such detailed information about your network topology. It’s a very specific case, and the fact that it works with an older 100Mbps router gives us a huge clue.
The issue likely isn’t with the Nucleus+ hardware itself, but rather a protocol conflict or an auto-negotiation erroroccurring between modern Gigabit hardware and the specialized components in your chain (like the Aqvox switch).
Here are the most likely reasons why your Wi-Fi band is crashing and what you can do to fix it:
The "Aqvox Switch" Factor & STP Loops
The Aqvox switch is often based on industrial boards that might have STP (Spanning Tree Protocol) enabled. Modern routers (Synology/TP-Link) are very sensitive to this. If the router detects what it perceives as a “network loop,” it may disable its own wireless radio or its internal switch to protect the network.
Test: Plug the Nucleus+ directly into the LAN port of your Synology/TP-Link router (bypassing the Aqvox switch). If the Wi-Fi stays stable, we’ve found the culprit.
IGMP Snooping & Multicast Storms
Roon relies heavily on Multicast traffic to discover endpoints. Some modern routers (especially TP-Link Archer series) can “panic” when they see high-volume multicast traffic on a Gigabit port and may stop broadcasting Wi-Fi to prevent a crash.
Fix: Go into your Synology/TP-Link settings and look for "IGMP Snooping". If it's ON, try turning it OFF(or vice versa).
IP Address Conflict
It’s possible the Nucleus+ is set to a Static IP that overlaps with the default gateway or a reserved range of your new routers.
Fix: Ensure the Nucleus+ is set to DHCP in its internal settings so the new router can assign it a fresh, valid address.
Port Negotiation (1000Mbps vs 100Mbps)
The old Linksys works because it’s limited to 100Mbps. This “slows down” the communication and avoids errors that occur at Gigabit speeds when specialized audio switches are involved.
Test: If your router settings allow it, try manually setting the LAN port connected to the Aqvox/Nucleus to "100Mbps Full Duplex" instead of "Auto".
Recommended Next Step
Please try connecting the Nucleus+ directly to the Synology router for 24 hours. If the problem disappears, we can then look into configuring the Aqvox switch or the router’s port settings to play nice together.
Hi Alex! The suggested connections and settings did not bring a solution. I connected the Nucleus directly to the router, it was not 24 hours, but the error did not disappear. Enabling “IGMP Snooping” did not bring any results either. The Nucleus, like all my Audio-video equipment, receives an IP address in DHCP based on its Mac address …1.111. I could not reduce the port speed on the router. However, I had time to do the following experiment:
I disconnected the devices from all ports of the Aqvox switch, except for the cable coming from the Synology RouterRT1900ac /8th port/. no error.
I reconnected the devices one by one:
LG OLED55G23LA TV 7th port no error
Onkyo PR-SC5508 AV proc. 6th port no error
Pioneer BDP-LX58 BD player 5th port no error
Zappiti Pro 4K HDR player 4th port !!!
NucleusPlus 3rd port !!!
Eversolo T8 audio player 2nd port no error
The presence of Zappiti Pro 4K HDR and NucleusPlus on the network at the same time causes the error, so the internet access on the wifi network is lost. I connect either one to the 2nd port, the error occurs after a few seconds. I remove either one from the network, the error disappears immediately. I currently have the Zappiti Pro 4K HDR turned off and there are no errors. This phenomenon occurs with all three routers, it should work correctly with the Synology RouterRT1900ac. That is my router and it worked fine for years.
Thank you
Gábor Kóródi
Thanks for the additional troubleshooting you’ve done so far!
Audiophile switches (like the Aqvox) are often optimized for jitter reduction but can sometimes handle network overhead (like Spanning Tree Protocol or heavy Multicast) differently than standard enterprise gear.
As a next step, can you disconnect both the NucleusPlus and the Zappiti from the Aqvox switch and plug them directly into the LAN ports of your Synology router?
If that doesn’t help, even with DHCP reservations, a “ghost” IP conflict can occur if a device has a hardcoded static IP internally that matches your reservation range.
Could you temporarily delete the MAC reservations for both the Nucleus and the Zappiti in the Synology settings. Let them pick up entirely random IPs from the DHCP pool.
While both are connected, use a network scanner (like the “Fing” app on your phone) to ensure both devices show unique MAC addresses. In rare cases, manufacturers use the same generic NIC (Network Interface Card) prefix which can confuse modern ARP tables.
It may also help to disable “Smart Connect” and give your 2.4GHz and 5GHz networks different names (SSIDs). And in the Synology/TP-Link settings, look for “Multicast to Unicast” or “IGMP Proxy” and toggle them OFF.
Hi Benjamin!
It seems that deleting the “DHCP revervation” solved the problem for both devices. The Nucleus immediately got a new IP address /…1.211/, the Zappiti still gets the previous …1.107, but the error is gone. Thank you for your help!
Gábor Kóródi
That is excellent news! It sounds like the IP conflict or a stale DHCP reservation was indeed causing the network to stall.
Since removing the DHCP reservations fixed the connectivity issues for both your Nucleus and the Zappiti, we’ll proceed to mark this thread as resolved and close it.
Should you run into any other issues or have further questions, please don’t hesitate to open a new topic.
