Page 1 of 1

SSH issues

Posted: Sat Jan 13, 2018 12:12 pm
by IanBlakeley
TP-Link TL-WDR3600 v1 with V1.10

After some initial problems has been running fine, I saw the notification about some source changes so was going to access via SSH to make the changes, but cannot get in, nothing has changed use SSH keys and the machine I am on can still access other stuff on the network with SSH keys. Eventually thought I'll turn password back on since the keys are being rejected and that doesn't work either. Definitely the right password Web gui access is okay and I can execute commands via webshell.

Code: Select all

ian@Bilbo / $ ssh admin@192.168.70.1 -vvv -p2222
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "192.168.70.1" port 2222
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.70.1 [192.168.70.1] port 2222.
debug1: Connection established.
debug1: identity file /home/ian/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/ian/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: Remote protocol version 2.0, remote software version dropbear
debug1: no match: dropbear
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 192.168.70.1:2222 as 'admin'
debug3: put_host_port: [192.168.70.1]:2222
debug3: hostkeys_foreach: reading file "/home/ian/.ssh/known_hosts"
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,kexguess2@matt.ucc.asn.au
debug2: host key algorithms: ssh-rsa
debug2: ciphers ctos: aes128-ctr,aes256-ctr
debug2: ciphers stoc: aes128-ctr,aes256-ctr
debug2: MACs ctos: hmac-sha1,hmac-sha2-256,hmac-md5
debug2: MACs stoc: hmac-sha1,hmac-sha2-256,hmac-md5
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: diffie-hellman-group14-sha1
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: sending SSH2_MSG_KEXDH_INIT
debug2: bits set: 1051/2048
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ssh-rsa SHA256:pjy7zl/fL6LTksMy+hVF6/9zgKkbDvTg0SG6R3+97b0
debug3: put_host_port: [192.168.70.1]:2222
debug3: put_host_port: [192.168.70.1]:2222
debug3: hostkeys_foreach: reading file "/home/ian/.ssh/known_hosts"
debug3: hostkeys_foreach: reading file "/home/ian/.ssh/known_hosts"
debug1: checking without port identifier
debug3: hostkeys_foreach: reading file "/home/ian/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/ian/.ssh/known_hosts:9
debug3: load_hostkeys: loaded 1 keys from 192.168.70.1
debug1: Host '192.168.70.1' is known and matches the RSA host key.
debug1: Found key in /home/ian/.ssh/known_hosts:9
debug1: found matching key w/out port
debug2: bits set: 1049/2048
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug2: set_newkeys: mode 0
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /home/ian/.ssh/id_rsa (0x55a2304495f0), agent
debug2: key: gargoyle (0x55a230455be0), agent
debug1: Skipping ssh-dss key id_dsa - not in PubkeyAcceptedKeyTypes
debug2: key: ian@Bilbo (0x55a230456e60), agent
debug2: key: ian@Bilbo (0x55a23045b1b0), agent
debug2: key: /home/ian/.ssh/id_dsa ((nil))
debug2: key: /home/ian/.ssh/id_ecdsa ((nil))
debug2: key: /home/ian/.ssh/id_ed25519 ((nil))
debug3: send packet: type 5
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/ian/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: gargoyle
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: ian@Bilbo
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: ian@Bilbo
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/ian/.ssh/id_dsa
debug3: no such identity: /home/ian/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/ian/.ssh/id_ecdsa
debug3: no such identity: /home/ian/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/ian/.ssh/id_ed25519
debug3: no such identity: /home/ian/.ssh/id_ed25519: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
admin@192.168.70.1's password: 
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
admin@192.168.70.1's password: 
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
admin@192.168.70.1's password: 
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey,password).
ian@Bilbo / $ 
Tried changing the password, logged back into the Web gui but still rejected via ssh both keys and new password. I see there was a similar case a while back and the answer was to re-flash, I tried loading the upgrade-bin file for 1.10 but the gui is just hanging, it doesn't seem to compete the re-flash.

Image

We did have a power cut a few days ago but everything seemed to be back okay, I have restarted a couple of times and no different.

Re: SSH issues

Posted: Sat Jan 13, 2018 2:02 pm
by d3fz
Did you manage to complete the reflash successfully, even with the GUI hanging afterward? If so, that's a known issue.

Re: SSH issues

Posted: Sat Jan 13, 2018 5:31 pm
by Lantis
Am I reading your logs wrong, or are you trying to ssh as “admin”?

You might want to try “root” instead.

Re: SSH issues

Posted: Sat Jan 13, 2018 9:50 pm
by IanBlakeley
Lantis wrote:Am I reading your logs wrong, or are you trying to ssh as “admin”?

You might want to try “root” instead.
Sorry yes Mea Culpa, no idea why I did that, it's not like I haven't logged in before via SSH. Damn, what an idiot...

Re: SSH issues

Posted: Sat Jan 13, 2018 9:59 pm
by Lantis
Lol :D at least it’s an easy solution