Connection Issues with Redmi 12T Pro and Rare Boulder 812 Disconnections (ref#0CDKI4)

[Alex_Wang]

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I see my Roon Server, but I still can't connect.

When you try to connect, what screen do you see?

· I see something else

Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.

· No, the issue remains the same

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *WiFi*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *MacOS*

Select any of the following components that are present in your local network setup

· *Mesh networks*

You mentioned a mesh network in your setup. Certain common mesh networks might require slight reconfiguration to support Roon.

· None of the above

Describe the issue

My setup consists of a Mac Mini 4 as the Roon server; a Synology 916 as the music file storage; and a Boulder 812 as the Roon Ready preamp. The main router is an Asus GT-AC5300, and the secondary router is an Asus AC86U, connected in AiMesh mode. I use an iPad Pro 2022, iPad Mini 7, and Redmi 12T Pro as remote control interfaces.

I am currently facing two issues. First, when I use the Redmi 12T Pro as the Roon remote control, I lose connection with the server when entering the Wi-Fi coverage area of the secondary router. However, if I turn off Wi-Fi and reconnect in the main router's area, I can connect normally. Additionally, Roon Arc works fine in the secondary router's area.
The iPad Pro, iPad Mini 7, Boulder 812, and a Windows host are all connected via Wi-Fi in the secondary router's area without these issues, and I can send commands to the Boulder 812 to play or turn on/off without problems. I kindly ask for help to resolve the connection issue with the Redmi 12T Pro, as it is very important to me. I do not have a second Android device to perform a reproduction test to determine if it is an issue with the Android system.

Second, after updating the Roon server version to 2.47 (build 1510), there have been very rare instances where the Boulder 812 loses connection. Even after restarting Roon, the Boulder 812, and the router, Roon still cannot display the device. This issue has only occurred once since the update and then recovered automatically. During that time, I was operating the Mac Mini 4, and I'm not sure if this might have contributed to the problem.

My English is not very good, so I asked chatgpt to help translate this paragraph. I hope your answer can be relatively simple. Thank you very much.

Best regards.

Describe your network setup

The main router is an Asus GT-AC5300, and the secondary router is an Asus AC86U, connected in AiMesh mode.

[Wade_Oram]

@Alex_Wang

First, when I use the Redmi 12T Pro as the Roon remote control, I lose connection with the server when entering the Wi-Fi coverage area of the secondary router. However, if I turn off Wi-Fi and reconnect in the main router’s area, I can connect normally.

This sounds like you still have the secondary router (the RT-AC86U) in ‘router mode’. When AiMesh is configured correctly on the secondary router it should be in AiMesh node mode (configured on the first tab of the ‘Administration’ page) :

I’m not sure if I can help with your second issue. It is possible that it is also caused by the same misconfiguration.

[daniel]

Hi @Alex_Wang,
Thanks for reaching out to us about this issue. @Wade_Oram’s suggestion for your first problem is correct. Please try his suggestion and let us know if it works.

For your second problem we will need to take a look at your Roon logs. The next time the Boulder loses connection please let us know the date and time that it happens, and we will look at your logs to find the event.

@Alex_Wang

My English is not very good, so I asked chatgpt to help translate this paragraph.

If you would prefer to correspond in a different language than English feel free to and we will do the translation ourselves.

[Alex_Wang]

I logged into the router to check and confirmed that I was using the aimesh node mode.Maybe my expression is not very accurate and there is a misunderstanding. If it is in ‘router mode’, the iPad should not be able to connect to Roon.

[Alex_Wang]

Unfortunately this didn’t solve my problem, my setup currently looks correct. Hoping for a possible solution.Screenshots of the network settings have been sent back to Mr. Wade.

[connor]

Hi @Alex_Wang,

Thank you for your troubleshooting so far. We have several more suggestions after having inspecting recent diagnostics from your RoonServer that automatically upload to our servers.

Here’s what we’ve found:

1. The Mac appears to have both a WiFi and an ethernet connection (or two WiFi connections). There are two IP addresses assigned intermittently on the same subnetwork. These appear to be provided by the same DHCP server in a single router. Try disabling the WiFi and relying entirely on the ethernet hardwire connection. This is separate from Tailscale/other VPN network interface (usually 100.7x.xxx.xx) which should remain active.

If you’re still encountering issues after restricting the connection to one network interface in step 1, move to step 2 below.

2. Enable any multicast forwarding on both routers and all mesh nodes. IGMP snooping must be enabled on the secondary router and mesh nodes as well. Roon’s device discovery traffic must be able to pass between these nodes, and these settings are often intertwined with basic multicast forwarding.

Please let us know if this helps. It looks like you rely on a VPN to use Roon. Take note that we’ll not be able to troubleshoot Roon’s access to upstream services, because the use of a VPN to bypass geographic restrictions is something we don’t have the capacity to troubleshoot. This particular situation seems to pertain to multicast forwarding within the LAN, so we can troubleshoot that component.

[Alex_Wang]

Thank you very much with @connor’s advice; I successfully resolved the issue.

In some past posts in the community, I only saw that IPTV needed to be enabled, but I didn’t know exactly where to do this until you mentioned IGMP Snooping. I entered the router interface and enabled the option, and the problem was solved. Now, the Android device briefly searches in the secondary router’s area, connecting to Roon after about half a second, which is great. I will attach a screenshot here in hopes of helping others who may encounter similar issues.

As for part 1, it does not seem to be the root of the problem. To test it, I reconnected to the Wi-Fi and was still able to connect smoothly, but I disconnected it for stability. I rely on a VPN to use Roon ARC, and so far, it does not appear to be affected. I am very grateful for the support provided by the Roon community.

Best regards.