@john
Hi John, I have a Nighthawk X6. The Vault 2 is a hardwire LAN connection from the Nighthawk, and the PC, which has the Roon Core, is also a hardwire LAN connection to the Nighthawk. Only the two Nodes are wireless. So the problem exists on both hardwire connections and wireless connections. I’ll try the Nighthawk firmware upgrade IGMP tests this weekend. Be advised, however, that at one time this system did work okay. I wouldn’t call it super reliable but it did work most of the time.
Thanks,
Robert
@john - I think we made some progress here. That link you sent me about the router not passing data from LAN to Wireless is close to what I see here. The Vault 2 is hardwire LAN connected but the Node 2’s are wireless. However, when I typed in http://www.routerlogin.com to access my router I get a page telling me I am not connected to the wireless network. I got the same result on MS Edge, Firefox, and Chrome. Consequently, I cannot upgrade the router. Windows 10 tells me I am connected to the wireless and I can access the internet, email, etc. but not the router. Bluesound OS can play music via wireless, my Logitech Squeezebox, and TV can stream Netflix movies all via wireless without a problem. I tried rebooting the router, pressing the factory reset button, but nothing has changed. I’ll talk to Xfinity about changing the modem from bridge mode to Modem and router mode.
@john - More data. i got this from doing ipconfig /all at the command prompt. I don’t see the Nighthawk router listed.
"
Microsoft Windows [Version 10.0.17134.829]
© 2018 Microsoft Corporation. All rights reserved.
C:\Users\Robert>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : WoobilyBear
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 74-85-2A-1A-79-A1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f8d4:2445:c8e2:3673%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, June 15, 2019 1:55:45 PM
Lease Expires . . . . . . . . . . : Sunday, June 16, 2019 1:55:44 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 158631210
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-41-F1-A3-74-85-2A-1A-79-A1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-15
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::488a:7e36:71f4:1475%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 671612967
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-41-F1-A3-74-85-2A-1A-79-A1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : 5E-E0-C5-6D-F9-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : 5C-E0-C5-6D-F9-AD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® Dual Band Wireless-AC 7265
Physical Address. . . . . . . . . : 3A-A0-51-E3-D8-71
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::acec:d188:97b0:106b%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, June 15, 2019 2:21:44 PM
Lease Expires . . . . . . . . . . : Sunday, June 16, 2019 2:21:43 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 272277585
DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-3A-A0-51-E3-D8-71
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TeamViewer VPN Adapter
Physical Address. . . . . . . . . : 00-FF-53-F7-20-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 5C-E0-C5-6D-F9-B0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
C:\Users\Robert>
C:\Users\Robert>
C:\Users\Robert>
@john - Progress of sorts. I called Netgear support and discovered that the router longin net address doesn’t always work and I have to log in via the IP address. I was able to verify I have the latest firmware already installed. Also, IGMP was and is disabled. They did a reboot of the router as well, however, it did not have an impact on Roon finding the Nodes. Speaking of firmware upgrades, there is a Beta HotFix release of 10.1.59, which addresses some security issues, but Netgear support didn’t install that one. The 10.1.54 is the current stable release, which is what is in the router.
@john - Bluesound gave me a list of things to try but none of them had an impact, Roon cannot find my devices. They suggested we continue to work with the Roon folks since from their perspective, everything is working okay. I’m not happy about that statement but there isn’t much I can say about it. So I am back to you folks, hoping we can resolve this. I am working from home on Monday, perhaps you can log in remotely and sort this problem out?
May be a long shot but I saw a post this morning from a person who was having intermittent problems with a wireless Bluesound device. He found that nearby wireless traffic was being broadcast on the same band he used. When he switched the wireless band in his router the problem went away.
@grossmsj - Interesting idea, I will check it out. However, that doesn’t explain why the Vault 2, which is ahardwire LAN connection, isn’t discovered by Roon.
Hello @Robert_De_Mattei,
Let’s try and remove Bluesound from the equation and see how general Roon Ready audio zone discoverability is working on your network.
Head over to the Roon Downloads page and grab the “Roon Bridge” package. Roon Bridge will turn a Mac or PC into a “headless” audio output on your network. The discoverability mechanism for Roon Bridge devices is nearly identical to Roon Ready devices like Bluesound.
Steps:
- Ensure that the “Roon” app is not running on the 2nd PC.
- Download and install Roon Bridge on a 2nd PC or Mac on your network.
- Using the Roon app on the Roon Core or a mobile device, check to see if the Roon Bridge PC appears in settings > audio.
I would periodically check that the Roon Bridge device remains discoverable over the course of 24 hours. The goal here is to determine if this issue is affecting how Roon is communicating with Bluesound devices on your network, or if this is affecting all Roon Ready traffic.
-John
@john I downloaded and installed Roon Bridge and I have it running on my Dell Laptop. Back here at the Roon Core, I went to Setting/Audio and clicked on the Scan for Devices circular arrow. However, nothing showed up. I let it running and will try a few more times periodically today. Given the situation here, I would guess it will not change if it didn’t find it at first.
@john Here is something. On the Dell laptop where Roon Bridge is installed, the icon appears in the task bar and clicking on it shows Ronn Status: Running however, it is grayed out. Is this normal?
I have it set to run at startup and rebooted the laptop but it is still grayed out and still stating it is running.
Hello @Robert_De_Mattei,
If you open task manager, do you see a process named “RAATServer.exe”? This process is what would be handling the communication with the Roon Core. If this is running, it should be operating normally insofar as the local Roon Bridge installation is concerned.
If RAATServer is running and cannot be discovered by the Roon Core, this suggests an issue with multicast discovery on the network that is not just limited to the Bluesound devices.
The next step is to localize where in the Core -> Router -> Bridge chain things are getting tripped up.
Looking your previous posts, it appears that you were able to reproduce the Bluesound non-discoverability issue while using another PC as the Roon Core. Can you clarify that this is correct? If so, there are two possibilities that could explain this behavior:
- The router is failing to pass multicast information between devices on the network.
- Some common piece of software on the two PC’s is effecting network traffic in the same way.
In both cases, I would ensure that any firewall software is disabled on the PCs before continuing with any other steps. It’s important to be thorough here, we have seen multiple cases where users had software running with firewall protection and didn’t know it was even an option. Go through all of the apps in your toolbar and take look at the running processes in Task Manager for any possible culprits.
On the router, ensure that the IGMP and multicast settings are correct. Another possible mechanism that could explain this behavior is IPv6 routing. Try disabling IPv6 routing on the Netgear, reboot the router and any networked devices and see if you notice any difference with discoverability.
You mentioned reaching out to Comcast and discussing changing the modem from bridge mode to router mode, were you able to explore this? Using a different router than you are currently would go a long way to eliminating all of the possible culprits here.
-John
1 Like
@john I restarted Roon Bridge on my laptop, which is running Windows 7. RAATServer is running in 32 bit mode. I also found Roon Helper and Roon Bridge in the operating list.
I then exited Roon Bridge and started Roon on the laptop. I had to “unauthorize” my PC as the Core and set the laptop as the Core. However, once this was completed, the laptop could not find any BlueSound device on the wireless network.
The firewall is controlled by the Avast Antivirus software. I made an exception for Roon, so Roon has full control of the network. However, Roon cannot find any devices on the network.
Question - I have been all through the NightHawk X6 setup and I cannot find anything relating to Multicast. Where and how do I check this?
As for running apps, all the applications are shut down and closed, but still no luck. I can disable the antivirus software and firewall completely by disconnecting the system from the internet and just using my local WiFi. If you think this is worth a shot, I will reconfigure the system and give it a try.
Befor I got my Unifi stuff I used a Netgear Nighthawk r7000 never had any issues.
@john Question - I have been all through the NightHawk X6 setup and I cannot find anything relating to Multicast. Where and how do I check this?
Also, I did not see anything on the Router page relating to IPv6. How do I disable this?
I’d rather explore all the Netgear options before having Infinity redo the modem setup.
Robert
Hello @Robert_De_Mattei,
For Multicast settings, you should be looking in the WAN settings for anything related to “Multicast” or “IGMP”. Try things with IGMP enabled and disabled and see if you are able to notice a difference in behavior. Be sure to reset the router and the Bluesound device when enabling/disabling the feature.
I believe you can find the IPv6 settings in the “Advanced” tab on the Netgear router.
-John
@john Hi John, I’ve been away on vacation and I am working on this problem again. I have confirmed that IPv6 is disabled.
I also confirmed that IGMP was disabled. I enabled it and found that there was no change - Roon cannot find the BS equipment. Currently, it is now enabled.
Interestingly, in the Attached Devices table, it does show the BS Nodes attached via wireless and also the Vault 2 in wired connections. The addresses match the BS application.
Next up is a different router as I have another Netgear router. I’ll try that tonight along with disabling the Xfinity modem.
Robert
Hello @Robert_De_Mattei,
When you were running these tests, did the Vault 2 appear in Roon as expected?
-John
@john No, with the exception of the speakers on my PC, nothing shows up in Roon, ever. Vault2, which is hardwired, or either Node 2, which are wireless.
I did connect up a different router, although it too is a Netgear Nighthawk R8000, and using this router, nothing shows up in Roon. I could play music through the Vault 2, however using the BlueSound app, but nothing in Roon. This router is set to its default settings, while the original R8000 router is set to the settings you and the BlueSound Support crew told me to set it. Note that, back in the day, I used the original router in its default settings and Roon would work. I am switching back to the original router now.
@john Please understand I will need some serious help here as the last time I was able to get Roon to work was back in March. All I can say is BlueSound had two updates between the last time Roon worked and the next time I tried to get Roon to work, however it has never worked since then. Unfortunately, the BlueSound Crew believes this is a Roon problem, rather than a BlueSound problem.
This may not be relevant, but my experience with Bluesound, Pulse 2,Pulse Mini and Pulse Flex
My endpoint all disappeared recently for no known reason. So I decided to factory re set one of the units whilst hard wired to network. This revealed an update had been delivered, and so I completed the update process.
Once this was done on all the devices, all the endpoints appeared in Roon and BluOS and all is working very well.
As I say, I don’t know if your units can be factory re set or if you have done this,