Comment 1 for bug 1777022

Juju 2.3 provides specific bind and ingress addresses to solve this sort of issue.

Some sort of fallback will of course be needed if we need to support older deployments.

Machines added with the manual provider may be a wildcard here, since their networking is not under Juju control. 'juju relate ... via ...' might help here (https://docs.jujucharms.com/2.3/en/developer-network-primitives), or an extra-binding (https://docs.jujucharms.com/2.3/en/authors-charm-metadata) to allow the rage to be specified at deploy time.