EOS 2.9 OSC Qlab intergration

Have also a look to this blog https://blog.etcconnect.com/2019/02/exploring-the-network-osc-part-ii/
The only thing that changed in 2.9 is the possibilty to use other TCP ports than 3032.

Thanks for the response, unfortunately i am still having the issue and have gone over everything again. 

Can you describe your issues and what the hardware setup and network configuration you use. 

The system i am using is;

Dell optiplex, win10, eos nomad 2.9 (master).

EOS IT 2.9 (backup) main interface

Dell optiplex, win7, eos nomad 2.9 (Client)

Apple airport handling Routing and DHCP

Parthport nodes using SACN

macbook pro for qlab 4 with 2 nic's 1 is the lighting network 2 is Dante

The problem is the OSC triggers from Qlab to EOS no longer work, (They work in 2.8), we have rolled the consoles back to 2.8 for the show.

The system i am using is;

Dell optiplex, win10, eos nomad 2.9 (master).

EOS IT 2.9 (backup) main interface

Dell optiplex, win7, eos nomad 2.9 (Client)

Apple airport handling Routing and DHCP

Parthport nodes using SACN

macbook pro for qlab 4 with 2 nic's 1 is the lighting network 2 is Dante

The problem is the OSC triggers from Qlab to EOS no longer work, (They work in 2.8), we have rolled the consoles back to 2.8 for the show.

you're sending the OSC strings to the master?

I tried to control EOS nomad 2.9 (WIN10 and macOS) by QLab4 with a hardwired network, it works
for me without a problem. The only thing I found out is that you need too switch off the wireless
network, because there is no NIC picker for EOS nomad.

Thanks for all the suggestions i will investigate and problem solve this once we are out of production on our current show and post the findings.