Single Companion Instance Controlling Devices on Multiple Networks

[indyvql]

I've been part of a volunteer livestream team for a few years now and we've been using Companion with Streamdeck for most of that time. It is a great product!

We've recently renovated the space and that has led to our network being split into an isoltated AV network and a general purpose network (with internet access). They are not currently connected to each other in any way.

We'd like to have a single Companion instance control devices on both networks and would appreciate recommendations on the best approach to doing this. The seemingly "simple" approach would be to have the computer running Companion have a network connection to both networks (2 ethernet or 1 ethernet + 1 WiFi).

Can Companion connect on multiple networks simultaneously? Would that be the best approach anyway? Unfortunately, we can't test much yet as the networks have overlapping IP ranges and we're working to get that changed.

Thanks in advance,
Torrey

[Julusian]

Yes that will work fine as long as you configure the network interfaces correctly.
Companion doesn't need anything special, it follows the os routing table when making connections.

[indyvql]

That's great, thanks for answering that for me. Not all software deals with multihoming well.

[sys724]

I'm running Companion on a computer connected to two different networks via two separate network interfaces in two distinct IP ranges. It works perfectly fine, but there's one slight issue:

When Companion is running on interface A, it can control devices on both networks just fine, but I can only send HTTP commands towards Companion on interface A, but not on interface B.

So, say, Companion is running on 1.2.3.4:9999, I can send POST requests like 1.2.3.4:9999/api/... and Companion receives those just fine. But, I cannot send anything to 5.6.7.8:9999, since on that second interface, Companion's port (9999in this example) is not open.

Is there any workaround to receive HTTP data on all network interfaces? Is this something I can configure, something that a future Companion release could include, or rather something that the OS (Windows 11) will not allow or will need to be configured in the OS somewhere?