Hi @thebiglebowski ---- Thank you for reaching out, your patience has been appreciated!
I had our techs spend some time revisiting your ticket, logs, and survey answers once more. As you are aware, we’ve been actively gathering data from users who have been reporting remote connectivity issues with Android, and as I’m sure you’re aware we have been working hard but still haven’t been able to pinpoint why some systems seemingly work with a variety of devices and remotes, but have issues specifically with Android Remotes and Linux Cores.
We continue to investigate why 99% of Android remotes work, but certain systems do not, and one of the biggest challenges is separating this issue from more generalized connectivity issues. Obviously, Roon works on tens of thousands of networks, but we field questions about all sorts of connectivity issues, and we need to handle network troubleshooting differently from the more specific Android issue.
The primary symptom of the other issue is that other remotes work (like Windows, OSX, etc) but Android does not. Since you are experiencing this with both your Android remote and your OS X remote, this points to something more generalized. It doesn’t preclude the Android-Linux issue, but at a minimum it points to something all going awry in your environment.
We were hoping the logs would yield a “smoking gun” and we could say ROCK was going unresponsive due to a clear crash, bug, or piece of media, but unfortunately we are not seeing anything in the logs that gives us a clear picture of what’s going on here.
This means our next step is really going to be network troubleshooting. I should be clear that this can take some time, but we do this regularly, and we are almost always able to pinpoint where the problem is, but it can require some patience.
So, you’ve mentioned the following in regard to your network configuration:
“WAN connection into untangle appliance as outside interface (VM DHCP) with inside interface (192.168.111.x) connected to a Cisco 2960G(192.168.111.x). Asus N66u (192.168.111.x) in access point only mode also connected to Untangle and this interface is bridged to the inside interface. All IP addresses are DHCP with the server running on the untangle appliance. Everything sits in vlan 1 on the cisco switch”
This is not the most complex network we’ve seen but it’s also not the simplest. As most people will tell you, the most foolproof way to to determine what could be causing this behavior is process of elimination.
My recommendation would be to remove as much complexity as possible, and confirm that things are stable. I would start with your NUC mounted directly to the mentioned Asus N66U with everything else disabled or moved outside the subnet temporarily.
If things are stable in that configuration, you can add the additional switches, firewall, etc back in one at a time, to verify where things are succeeding and where they are failing.
If things are not stable in a simplified environment, please get back to me with the exact topology and what went wrong, as well as another set of logs – then we can get a better sense of what’s going on here, and start ruling out environmental factors, cables, hardware issues, bugs, etc. I’m sure we can figure this out so thanks in advance for your patience @thebiglebowski!