I’m not 100% sure, but I think it confirms two things. First, your Nucleus is OK. All we’ve done is change the way it’s connected to your network and force it to use better DNS. Second, I think we’ve also confirmed that this problem isn’t anything to do with REIN or SHINE.
If this latest test/setup stops your router from restarting every 15 minutes I think we can also conclude that adding a new router (in addition to the HH4, not instead of it) will also fix the problem.
I’m not getting too excited yet though, as it’s only been an hour, but it’s looking hopeful.
Correct me if I’m wrong: I think the Mac OS is behaving as a router, you’re doing double NAT, and the reason it does not cause the reboot of the router is that multicast is blocked by the Mac OS, not flooded to the router this way.
Although double NAT is a bad thing and should be avoided, in the OP’s situation where the router cannot be turned into bridge mode, and being unable to the change the router, adding a second router is indeed a possible solution to consider (if it works), when no better solution is found.
I think a smart hub 5 for business which you can get for a tenner off ebay will do what you want and you can change the DNS servers on it which is always good for roon speed.
Login to BTHub5Goto Advanced SettingsClick on the Broadband top level menuThen click on Internet(Which should be the default view)
When on this page you see all of the related Internet configuration info including BT DNS servers. Next you do as follows:
Click the disconnect button at bottom right of page(be aware this will disconnect your broadband connection)Once disconnected you will see an option for DNS which you can change from auto to manualSelect manual and you will get 2 boxes appear below to enter your manual DNS servers.Once DNS details have been added you simply reconnect to re-establish the broadband connection and hey presto, you have your own DNS servers configured.
Yep, that’s what I meant by “change the way it’s connected”, I just didn’t go into detail. As for blocking multicast - yes, this is probably the reason but resolving the DNS issue was clearly a priority too.
I went over this earlier. I agree, double NAT can cause problems, but only when you have two routers dishing out identical IP addresses on the same LAN. If you avoid this, and that’s really quite easy to do, there are no other downsides that I’m aware of.
There are probably many different models of routers from the same ISP. They are not made by the ISP, however. They are sourced from multiple suppliers based on price and other factors, according to specs - mostly the GUI branding and removal of advanced features (such as bridge mode and DNS). Even with the same model number, different hardware revisions can be totally different.
The most common issue with double NAT, in the context of Roon, is a user connecting a Roon-related device (e.g. Roon Core) to the 1st router, then connects another Roon-related device (endpoint or Remote app) to the 2nd router. This does not work.
It frequently happens whenever a user find that their ISP router WiFi is not good enough, then add another WiFi router or mesh to improve the WiFi, but finding that Roon no longer works. From time to time I encounter these cases, as Lumin native app basically shares the similar multicast requirements as Roon.
Just found this thread as I have been experiencing similar problems with my network. Many internet drop outs and reboots of BT Hub4 however not with the same fixed frequency as DJM.
I called BT and was visited by a technician. He could find no fault with the BT connection which is Fibre to the Cabinet and UG 350 yards Copper landline to the house.
Problems began at approximately the same time as DJM experience and coincidentally download of September Roon 1.8 release.
My system network had previously performed flawlessly for many years both with Sooloos and Roon.
Some time ago I upgraded BT service and received a replacement Smart Hub2 which I could not install as Internet is fed by BT Modem at Point of entry and wired by concealed Cat 6 cable to BTHub 4 on my desk.
I am no expert on these matters, and will continue to follow this thread for any further developments.
I am not entirely convinced in my case that it is my Nucleus RevB that is causing the dropouts as they also occur when Roon is not playing.
Thanks for your response Peter.
Forgot to mention that the BT technician swapped the BT Hub4 for a probably used replacement of unknown origin from the back of the van. However the PS was not changed.
Yes, sounds like you have a similar issue. The Roon software update, more or less coincides with the Reboots. which started roughly on 23 Sept. It was solid as a rock for 3.5 months.
The reason that I was given a HH4, Type A, is because we have an ‘Exchange Line’ which is overground, directly from the Exchange, and not the Green Fibre Cabinet.
I have a temporary fix at the moment, courtesy of @DaveN. For reasons unknown, the Nucleus no longer likes the BT HH4 (Which was replaced last week). The long term solution for me, is to get a new third part Router, such as a TP-Link Archer C2300.
I have informed @Dylan of this issue, but it may be a good idea for you to do the same, quoting my post. Just in case it is a Roon software glitch that doesn’t like the old BT HH4.
Hi @DJM & @Hector, Another thing that might be worth trying if you haven’t already — If you have the option to disable IPv6 on your network does that help at all?
I was sure that I read that the HH4 didn’t do IPv6, but it looks like it can. To see if it makes a difference you’ll need to turn it off, maybe reboot the hub, then reconnect the nucleus to the hub. Keep us posted.
This was the source that lead me to believe the HH4 couldn’t do IPv6.
Yeah, I didn’t think it would help. And you can reenable IPv6 if you want, but as it can cause other issues with Roon you may as well leave it turned off for when we do manage to get things up and running properly. It’s not necessary, and it will likely cause problems further down the line.
New router. That’s the only current plan we have that makes any sense
For reasons unknown, the Nucleus no longer likes the BT HH4 (Which was replaced last week). The long term solution for me, is to get a new third part Router, such as a TP-Link Archer C2300.
