CHANNEL SIZE.

[Terry Shipclark]

debug1: Remote protocol version 2.0, remote software version 4.1.2 SSH
Secure Shell Toolkit
debug1: no match: 4.1.2 SSH Secure Shell Toolkit
debug1: Enabling compatibility mode for protocol 2.0

Is the one that doesnt connect.  I did some more testing, and there older
hardware on the extremeware platform will still connect.  Newer Hardware
will not.

old hardware

debug1: Remote protocol version 2.0, remote software version 2.0.12
(non-commercial)
debug1: match: 2.0.12 (non-commercial) pat 2.0.11*,2.0.12*
debug1: Enabling compatibility mode for protocol 2.0


Like I stated earlier changing the Default window size back to 4 solved the
issue, and everything else works fine.  Full DEBUG output is attached

On Thu, Apr 24, 2008 at 3:49 AM, Markus Friedl <markus.r.friedl at arcor.de>
wrote:

> On Wed, Apr 23, 2008 at 12:22:53PM -0400, Terry Shiplcark wrote:
> > 4.7p1 would no longer allow me to connect to the switches, however 4.6p1
> > would. The error I received was.
> >
> > ' channel 0: open failed: resource shortage: Channel open failed'
>
> yes, that's strange. it looks like a bug in the switch since
> we only increased the size that openssh claims it can receive
> and not the buffer sizes on the remote side.
>
> do you have the ssh version string of the switch?
>
> ssh -v prints it as
>        debug1: Remote protocol version X.Y, remote software version ZZZ
>
> -m
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debug_output.txt
Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20080424/bf9d2915/attachment.txt