Comment 2 for bug 1970289

I believe the goal was to be able to set something that would stick in a
given model, since all the machines are already deployed that way, and
James didn't want other people coming to that system to have to remember
--port and/or what port.

I'm also not sure that '-p' actually works for what Juju is doing. Because
we do pass '--port' to openssh, but I don't think we use --port for juju
itself to target the reachability check. (eg, if you have 3 addresses,
which one should be used for ssh, depends on where your client is, what
routes you have. so we would need a way to update *our* logic to also be
able to target an alternative port)

On Tue, Apr 26, 2022 at 5:10 AM Juan M. Tirado <email address hidden>
wrote:

> Would the --port argument enough in your case?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1970289
>
> Title:
> Units with multiple IPs and SSH on a non-standard port fails
> reachability check
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1970289/+subscriptions
>
>