We recently enable SSH2 in our environment. I am able to SSH to Cisco switches without any issue but can not to any Extreme switch. I can login to them fine via teraterm/secureCRT but not via Ubuntu.
I have a Ubuntu 14.04 machine. Here is what I am getting:
ssh admin@extreme_switch.com
ssh_exchange_identification: read: Connection reset by peer
With -v for more info:
ssh -v admin@extreme_switch.com
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to extreme_switch.com [10.10.0.99] port 22.
debug1: Connection established.
debug1: identity file /home/admin1/.ssh/id_rsa type -1
debug1: identity file /home/admin1/.ssh/id_rsa-cert type -1
debug1: identity file /home/admin1/.ssh/id_dsa type -1
debug1: identity file /home/admin1/.ssh/id_dsa-cert type -1
debug1: identity file /home/admin1/.ssh/id_ecdsa type -1
debug1: identity file /home/admin1/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/admin1/.ssh/id_ed25519 type -1
debug1: identity file /home/admin1/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
ssh_exchange_identification: read: Connection reset by peer
I was just about to suggest the same thing. I like this better than modifying the ~/.ssh/config file, since it will error out at first (with just ssh), and let you choose to downgrade to older, less secure algorithms.
Instead of typing the -o... on the command line every time (or more often, depending on your skill to avoid typos), you can also put it into your ~/.ssh/config file. See https://www.openssh.com/legacy.html
Lazy fat-fingered me would probably do that 😉
I did try Bernhard Gruenwald and Frank's solution but it did not work. I will try again and capture error message. I am not sure about that debug file, I will check other 870s
