debug3: send packet: type 90 # This was the request to open a new channel (SSH_MSG_CHANNEL_OPEN) debug3: receive packet: type 91 debug2: channel 1: open confirm rwindow 12288 rmax 512 # That was the Ok response (SSH_MSG_CHANNEL_OPEN_CONFIRMATION) debug3: receive packet: type 1 Received disconnect from 10.10.3.6 port 22:2: Disconnect Protocol erro +r # And then, suddenly, an unexpected disconnect message saying "Prot +ocol error"
It is not completely uncommon for some SSH implementations, specially those found in network equipment, to not support more than just one session per connection or requiring it to be open at some specific time (i.e. just after the transport layer becomes ready). There is not much you can do to work-around these issues.
Net::SSH::Any has the Ssh_Cmd backend which uses ssh in the common way, but then you can not combine it with Net::Telnet. At least, not easily. Net::SSH::Any provides the pipe method, which returns an object emulating a socket... maybe the emulation is good enough for Net::Telnet... I don't know, never tried!
In reply to Re^3: Net::OpenSSH multiple sessions and legacy KEX problem
by salva
in thread Net::OpenSSH multiple sessions and legacy KEX problem
by pwlodawi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |