Re^4: Net::OpenSSH multiple sessions and legacy KEX problem

Just to conclude, there is no way to use Net::OpenSSH with only one session ?

OpenSSH command line client opens only one session and it works even with this buggy implementation.

You are right that router's implementation is bad but I can do nothing about that. It's legacy device and there are no chances for new fixed version. I don't have to use Net::Telnet. Having it would make migrating some scripts easier but it's not a must have.

What I don't like in Net::SSH::Any::Backend::Ssh_Cmd it that is going to open a new connection for each command. Right ?

Anyway, thanks for your help

Pawel

Comment on Re^4: Net::OpenSSH multiple sessions and legacy KEX problem

Replies are listed 'Best First'.
Re^5: Net::OpenSSH multiple sessions and legacy KEX problem by salva (Canon) on Feb 16, 2018 at 19:42 UTC
Just to conclude, there is no way to use Net::OpenSSH with only one session? You are not doing anything fanciful, the basic stuff just doesn't seem to work. I can not imagine how you could avoid that issue. What I don't like in Net::SSH::Any::Backend::Ssh_Cmd it that is going to open a new connection for each command. Right? Not exactly. `Ssh_Cmd` runs a new connection for every session. Usually, when the remote side is some server running some Unix/Linux, you run a command per session but in the case of network equipment frequently they provide some custom shell that requires running a conversation against it and executing all commands in the same session. The fact that you want to use Net::Telnet hints in that direction.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Net::OpenSSH multiple sessions and legacy KEX problem
by salva (Canon) on Feb 16, 2018 at 19:42 UTC

Just to conclude, there is no way to use Net::OpenSSH with only one session?

You are not doing anything fanciful, the basic stuff just doesn't seem to work. I can not imagine how you could avoid that issue.

What I don't like in Net::SSH::Any::Backend::Ssh_Cmd it that is going to open a new connection for each command. Right?

Not exactly. Ssh_Cmd runs a new connection for every session. Usually, when the remote side is some server running some Unix/Linux, you run a command per session but in the case of network equipment frequently they provide some custom shell that requires running a conversation against it and executing all commands in the same session. The fact that you want to use Net::Telnet hints in that direction.

[reply]
[d/l]