We are having all kinds of issues with this at a home right now.
However, ours is actually behaving a bit differently than yours.
For some reason, we can't change the hostname to a static IP address.? The second we try this; the CH processor changes the status to awaiting authentication.
The device says that it is online, but the processor doesn't allow for any config changes or routing.
I have tried manually entering the CS authentication credentials through console, but nothing gets the device to show online in CH setup.
Crestron is confused, and their solution is to suggest that we put everything on the same subnet.
We have VLANs for a reason!!!!
What is even stranger, when you select the "Web Configuration" text in CH setup, it tries to load the NAX AES67 IP address not the management one.
Of course, once I select "Repair Connection" in CH setup, it forces the hostname again.
Oh ... and don't bother trying to put the NAX/NVX back on your control network because it doesn't work.
That's what I tried, with the Management on the clients network for Airplay.
No worky!? That's when Crestron tries to manage the device using the AES67 network!
Crestron ... please learn how to properly implement a VLAN strategy on a processor!
Instead of just giving us a place to input a range of addresses, why not just make the processor VLAN aware?
The processor should have an advanced networking tab that allows for entering the VLANs that should be allowed and the IP address of the processor on that VLAN.
This is the exact implementation in devices like the Josh.AI Core and OvrC Hub.
Or ... better yet Crestron, let us actually set things up in CH!
Stop trying to dumb things down just to get everyone on planet earth to install CH.
Just give classes on VLAN tagging and proper multicast implementation.
It drives me absolutely nuts that their answer is a flat network with everything in DHCP.
And let's not get started on trying to keep organized IP tables and Cresnet address ranges.
If anyone has successfully implemented this with the latest OS4 firmware, please chime in!
Brian
