Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mosh does not take care from some options in ~/.ssh/config file #978

Closed
tootai opened this issue Jun 9, 2018 · 1 comment
Closed

mosh does not take care from some options in ~/.ssh/config file #978

tootai opened this issue Jun 9, 2018 · 1 comment

Comments

@tootai
Copy link

tootai commented Jun 9, 2018

Hi,

we connect to customers servers using an ssh server, customers servers running autossh@reboot

At tech side we have in .ssh/config

Host myHost ; doesn't need to have a DNS entry
User myUser
Port 12345
ProxyCommand ssh ourssh.central.server.TLD nc localhost 54321 ;this being the port where autossh connect to

With this set up, a simple ssh myHost does connect to the customer server. We would expect that mosh does the same but no, we receive:

/usr/bin/mosh: Could not connect to myHost: Aucune adresse associée avec le nom de l'hôte
ssh_exchange_identification: Connection closed by remote host
/usr/bin/mosh: Did not find remote IP address (is SSH ProxyCommand disabled?).

where Aucune adresse associée avec le nom de l'hôte means no address related to the hostname.

Would be a nice feature if mosh would have the same behavior as ssh.

Daniel

@andersk
Copy link
Member

andersk commented Jun 9, 2018

Duplicate of #285. You may be able to use the new --experimental-remote-ip option described there, although keep in mind that Mosh traffic cannot be proxied at this time—this only affects the short-lived SSH connection that mosh makes at startup to launch mosh-server.

@andersk andersk closed this as completed Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants