I too have gotten the same error, most notably when
crossing the OS threshold (BSD -> Sol, Sol -> BSD,
Linux -> BSD, etc.).
I've posted on several different lists with full debug
logs, etc. over the past few weeks and haven't even
gotten a decent flame...
I think that either the problem we are seeing is so rare
that none of the guru's beleive it even when they see
the logs, or, it's so complex that it's taking awhile for
them to think of an answer.
Until then, I'm forced to use SSH v1 instead of v2 when
I go to a disparate OS.
On Mon, 15 Jan 2001, Ben Ricker wrote:
> Date: Mon, 15 Jan 2001 10:07:47 -0600
> From: Ben Ricker <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: 'Bad Packet Length' error?
>
> After upgrading my client with 2.4p1, I started getting the folowing
> errors when using slogin to login to a server:
>
> 2f 75 73 72 2f 6c 6f 63
> Disconnecting: Bad packet length 796226418.
>
> Thinking it was the 2.4 upgrade, I uninstalled 2.4 and reinstalled 2.3
> client. Problem still exists. I have OpenSSH 2.3 installed as the server.
>
> I even deleted the key entry on the client side by editing the
> 'known_hosts' file. Still get that error message. Strangely enough, I
> can ssh into other boxes and then ssh into the box I cannot ssh into
> directcly!
>
> Any ideas?
>
> Ben Ricker
> Senior Web Administrator
> US-Rx, inc.
>
>
