The remote host names people want to put into their VisIt host profiles can often be derived from their ~/.ssh/config file. If I have something setup such that ssh my-fav-anl-machine at a shell prompt works. They want to put my-fav-anl-machine as the remote host to connect to in VisIt.
This seems perfectly reasonable to me.
In networks where compute nodes are behind firewalls, the real machine VisIt is connecting to is not know to the local host. We use a gateway or ssh tunenling or control master to connect to it.
But, VisIt will immdiately return "Invalid host" message for that hostname and not ever attempt the connection.
This is happening on ANL systems which have quite a substantial set of constraints on various intermediate nodes before one can log into a compute node.
Describe the bug
The remote host names people want to put into their VisIt host profiles can often be derived from their
~/.ssh/config
file. If I have something setup such thatssh my-fav-anl-machine
at a shell prompt works. They want to putmy-fav-anl-machine
as the remote host to connect to in VisIt.This seems perfectly reasonable to me.
In networks where compute nodes are behind firewalls, the real machine VisIt is connecting to is not know to the local host. We use a gateway or ssh tunenling or control master to connect to it.
But, VisIt will immdiately return "Invalid host" message for that hostname and not ever attempt the connection.
This is happening on ANL systems which have quite a substantial set of constraints on various intermediate nodes before one can log into a compute node.
https://help.cels.anl.gov/docs/linux/ssh/
Finally, are we in all circumstances using a user's "ssh env." to connect to hosts the user would otherwise normally and easily connect with via ssh?