Issues come in these networking setups, when the user is just connecting network segments to different NICs without making sure to use different IP ranges.
Like, if you have NIC1, and NIC2, both on 10.0.0.0/24 IP,
the metric of NIC1 gives it higher priority
and you try to send OSC from Resolume to a device, which is connected physically to the NIC2 segment,
and the two segments themselves are not connected.
With OSC, the system will use the routing table, sends the packet on NIC1 as it's higher priority and matches the IP range of the destination.
This is the same behavior as in any other programs which rely on the system routing.
The easy solution is to double check the network ranges. The harder one is managing the system routing table IMO.
Limiting OSC input and output to a specific adapter would take a lot of flexibility out of possible setups.
With DMX you probably only have one console to control everything, but with OSC, you could have multiple phones or tablets sending interactive stuff.
NDI handles networking inside the library provided by Newtek. Unfortunately we don't have any means to control how it behaves.
Moving this to feature requests, so you can vote