SSH connection to CISCO cannot be established - WeOnlyDo Discussion board

SSH connection to CISCO cannot be established (wodSSH / wodSSH.NET)

by Tomas Malecek, Tuesday, December 04, 2018, 13:54 (6 days ago)

Hi *,

We have encountered problem using wodSSH.NET library together with CISCO switch.

Traces from CISCO cannot be obtained but from Wireshark I can see that CISCO does not responds to initial offer "Protocol (SSH-2.0-WeOnlyDo.Net)".

We have traces from other devices(and servers) and it is working, however I see that most SSH servers are unable to match the software version "weonlydo.net". Although they switch to compatibility mode and SSH connection is established.

CISCO switch SF350-24 with firmware version 7.3p1
wodSSH.NET version: 2.6.4.162

Traces from debian server (working SSH):
Nov 19 10:55:05 ENG-AUS-COR-408 sshd[19218]: Connection from 10.199.77.53 port 51207 on 10.199.77.5 port 22
Nov 19 10:55:05 ENG-AUS-COR-408 sshd[19218]: debug1: Client protocol version 2.0; client software version WeOnlyDo.Net
Nov 19 10:55:05 ENG-AUS-COR-408 sshd[19218]: debug1: no match: WeOnlyDo.Net
Nov 19 10:55:05 ENG-AUS-COR-408 sshd[19218]: debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4
Nov 19 10:55:05 ENG-AUS-COR-408 sshd[19218]: debug1: Enabling compatibility mode for protocol 2.0

SSH connection to CISCO cannot be established

by wodSupport, Tuesday, December 04, 2018, 14:13 (6 days ago) @ Tomas Malecek

Hi Tomas,

if you telnet to CISCO on port 22 and paste same initial greeting as wodSSH.NET, ending with newline, what happens?

If should be something like SSH-2.0-WeOnlyDo.NET . Does CISCO reply in that case? Does he reply in small changes in your initial greeting text? Does it reply (it should...) even without pasting anything?

Jasmine.

SSH connection to CISCO cannot be established

by Tomas Malecek, Friday, December 07, 2018, 11:39 (3 days ago) @ wodSupport

Hi Jasmine,

thanks for swift reply. I have contacted customer (that's why my response took longer).

It seems that CISCO device is completely silent. I suggested customer to open ticket with CISCO support.

[image]