Eos OSC discovery doesn't rebind when the console has an interface that starts down and goes up after launch

Question

Tested on both ETCnomad and an Apex 5 console, both by accident. 
 
 Both running 3.2.9 
 
 I wrote some software that uses the OSC discovery server which is how I found this out. It turns out that if a network interface was connected after boot, the discovery does not start properly. This is most notable when trying to use the mobile apps. 
 
 Prerequistes: 
 - visible to remotes enabled in config 
 - remotes themselves enabled on all interfaces

Steps to reproduce: 
 - launch console and Eos software with a network connection not connected or up. 
 - Realise the network connection is not up and plug in the disconnected Ethernet cable. 
 - Expect OSC Discovery to function properly. 
 
 This is furthermore an issue because that server doesn't necessarily properly bind in eg, the event where a power outage occurs, the console is on a backup, but the switch its connected to is not.

Hans.Hinrichsen · Accepted Answer

Thanks for this report - good find! We fix this in a future 3.2.x patch (tracked as EOS-56230). In 3.2.0, we added a number of changes that allowed network connections to change after the console launched, but this was overlooked. 
 As a workaround - until the fix is implemented - you should be able to toggle the Visible to Remotes setting to restart the discovery service. 
 Finally - even with this change, there are some services that still require the network connection to be active at launch - multiconsole being the most significant one. There is a setting in the shell (Settings -> Network) called "Required" (and in 3.3 will be called "Delay Eos launch until interface is online"). You should enable that on any network that is required for the show to run properly, and it will prevent Eos from starting until that condition has been satisfied.

Eos OSC discovery doesn't rebind when the console has an interface that starts down and goes up after launch

Top Replies