Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- ssh tunnel misbehaving.
- William Unruh
January 13, 2015, 9:34 pm
rate this thread
antoher machine B. On A I run autossh
autossh -M0 -R 8022:localhost:22 B
The connection appears to be made (autossh keeps running, and one does
not get repeated reconnections). On B it seems as though there is some
sort of connection
ssh localhost -p 8022
will not complain, but will also not connect to sshd on the remote
machine. It just sits there doing nothing.
There does not seem to be any clues either on A or B in the logs as to
what might be going on.
sshd is running on A and B.
These are both Linux machines ( Mageia 2 and 3 on A and B). B is
in A's /etc/hosts files. and I see the connection come up in
/var/log/messages on B.
Jan 13 12:07:42 B sshd: Accepted publickey for <user> from
A-IP port 35424 ssh2
(Yes, A is clearly an NAT connection to the net)
and ps auxww |grep sshd
lists that user as connected. autossh is running on A.
I cannot see any indication of any connecion or open port 8022 on B
ssh -v -v -v localhost -p 8022
OpenSSH_6.1p1, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 49: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 8022.
debug1: Connection established.
debug1: identity file /disk9/home/user2/.ssh/identity type -1
debug1: identity file /disk9/home/user2/.ssh/identity-cert type -1
debug3: Incorrect RSA1 identifier
debug3: Could not load "/disk9/home/user2/.ssh/id_rsa" as a RSA1 public
debug1: identity file /disk9/home/user2/.ssh/id_rsa type 1
debug1: identity file /disk9/home/user2/.ssh/id_rsa-cert type -1
debug1: identity file /disk9/home/user2/.ssh/id_dsa type -1
debug1: identity file /disk9/home/user2/.ssh/id_dsa-cert type -1
debug1: identity file /disk9/home/user2/.ssh/id_ecdsa type -1
debug1: identity file /disk9/home/user2/.ssh/id_ecdsa-cert type -1
And that is where things hang forever.
I have no idea what that " could not load .... as an RSA1 publc key"
means. since that same id_rsa is used on loads of other machines.
I get the same complaint then but the connection is fine. So it seems my
machine B is not communicating with A.
And a month ago this all worked fine.
- » Pros and Cons of using sftp-server as shell vs other methods of restricting interactive lo...
- — Next thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum