When setting up DMXRouter, I attempted to use the Switch function to switch between two different inputs across two VLANS and output a higher priority to step on a lower priority source on a third VLAN. I found the data to be unstable and removed the integration of Hyper-V in an attempt to "simplify" my setup. When using separate NICs, I was still having stability issues. So, I simplified further. I changed it to one VLAN of source sACN data, and one VLAN for the resulting destination data, forwarded at a 1 to 1 setup. The configuration was as follows:
VLAN "OA2" - NIC 1 - I.P. 10.21.1.253 /16 - Input data with Universes Ranging from sACN 1001 to 1210 (only 42 universes picked out from there, but it's easier to shotgun it from the desk).
DMX Router - Picks out 42 Universes and outputs it to:
VLAN "sACN" - NIC 2 - I.P. 10.6.1.253 /16 - Output the 42 selected universes at priority 150 so it will override the priority 100 data that already exists for those universes on this VLAN.
Expected Result: sACN Data from "OA2" overrides sACN Data on "sACN" to allow opening act to use the selected portions of the lighting rig.
Seen result: sACN Data from a third VLAN was bleeding through and taking over. This VLAN has a NIC IP of 10.20.1.253 /16 and while it is enabled in the DMXRouter software, it is not configured in the merges that were enabled. The sACN data would collide (since they were both priority 100) and the resulting output would be constantly swapping back and forth between the two inputs.
File attached for reference.
OA Merge.json
When setting up DMXRouter, I attempted to use the Switch function to switch between two different inputs across two VLANS and output a higher priority to step on a lower priority source on a third VLAN. I found the data to be unstable and removed the integration of Hyper-V in an attempt to "simplify" my setup. When using separate NICs, I was still having stability issues. So, I simplified further. I changed it to one VLAN of source sACN data, and one VLAN for the resulting destination data, forwarded at a 1 to 1 setup. The configuration was as follows:
VLAN "OA2" - NIC 1 - I.P. 10.21.1.253 /16 - Input data with Universes Ranging from sACN 1001 to 1210 (only 42 universes picked out from there, but it's easier to shotgun it from the desk).
DMX Router - Picks out 42 Universes and outputs it to:
VLAN "sACN" - NIC 2 - I.P. 10.6.1.253 /16 - Output the 42 selected universes at priority 150 so it will override the priority 100 data that already exists for those universes on this VLAN.
Expected Result: sACN Data from "OA2" overrides sACN Data on "sACN" to allow opening act to use the selected portions of the lighting rig.
Seen result: sACN Data from a third VLAN was bleeding through and taking over. This VLAN has a NIC IP of 10.20.1.253 /16 and while it is enabled in the DMXRouter software, it is not configured in the merges that were enabled. The sACN data would collide (since they were both priority 100) and the resulting output would be constantly swapping back and forth between the two inputs.
File attached for reference.
OA Merge.json