Build 1202 broke my local setup (unsupported, multi-VLAN config)

[Robem]

Hi David,

I noticed almost identical behavior recently, the difference is that the symptoms for me manifested in ARC being unavailable at times. I posted a feature request to have some control over the IP address that ARC uses but I now believe that your symptoms and mine are closely related.

Control Which IP Address Roon Core Listens On For ARC Connections

Can we add some kind of control over what IP address Roon Core listens to for incoming ARC connections? I have dual NICs in my core, the second one is for data transfer (library backup primarily) purposes and I find that the IP address that Roon Core is listening on fluctuates from time to time. I cannot gauge the consistency of this as it seems to have a mind of it’s own. Sometimes it is listening on the primary NIC, others it is listening on the data transfer NIC. Some way of controlling this…

Also, I want to mention that I don’t think that this issue should be classified as unsupported and I also question whether “Tinkering” is the right area for this. Is there somewhere where RoonLabs state that multiple interfaces renders your installation unsupported? I use RoonOS for my core and that is totally locked down, I consider that if I can configure RoonOS to do something (multiple interfaces as an example) that it should be fully supported and also not considered Tinkering. This is a feature and specific configuration that has been made available to us by RoonLabs.