@d2r Agreed. The network configuration of my development environment (laptop) is not what you'd typically find in a data center ;) (wifi coming/going, ethernet plugged in/unplugged, various vpn connections -- some that change my hostname, net interfaces for VMWare/Virtualbox). Plus I rarely reboot. So it actually worked out well as a "misconfiguration canary". I also purposefully messed with things to come up with the most misconfiguration-proof defaults.

In the end, keeping the nimbus host and tracker bind address separate, as well as the 0.0.0.0 default seemed to be the most foolproof. Some storm users struggle with network config and I didn't want to make it any worse.