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

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.

Related