l0k18
commented
3 years ago this is mostly done by the update stuff for multicast at least. all of the components will stop working when the network stops, and probably don't restart properly when a connection reappears. so we'll leave this one open specifically related to mobile builds but for laptops too really.
The controller is set up to use all available multicast channels and provides all known interfaces that are automatically bound to the listeners across messages passed over multicast. The addresses are used by other controllers to identify peers with a multicast zone in common and automatically peer them.
It is not important for desktop or server installations, but laptops, tablets and smart phones all will have changing IP addresses as they hop on and off wifi networks while moving around. Thus there needs to be a watcher process that can reinitialise the list of addresses so no stale paths are tried when they are no longer connected.