TCP port forwarding troubles?

[Rob Russell]

(I just subscribed and am replying to a message found in the archive.
I apologize for any malformed headers or quotations.)

On Jan 2, 2000 at 12:42, Markus Friedl wrote:
> On Thu, Dec 30, 1999 at 02:22:09AM -0800, Phil Karn wrote:
> > Before I dig into the problem, has anyone else out there heavily
> > exercised TCP port forwarding in openssh?
> yes, i experience this, too, but no, i did not look into this yet.
> i am using portforwarding for connections to webproxies, too.
> i think, the problem has been fixed in ssh-1.2.2x since i remember
> having the same problem with older versions of the 1.2.x family.

Do you believe it to be a server or client-side issue?  I'm having trouble
port forwarding (remote access to CVS) from an F-Secure SSH client for
MacOS to a server running openSSH 1.2.  

I can't reproduce this error with other client platforms (Other MacOS SSH
programs don't support port-forwarding), so it might be an issue with the
client, though the client worked with the 1.2.27 server.

Here's the logs, any input anyone would have would be greatly appreciated.

Dec 30 16:41:47 zathras sshd[8693]: log: Connection from 192.168.5.2 port
2057
Dec 30 16:41:47 zathras sshd[8693]: log: PAM Password authentication
accepted for "username"
Dec 30 16:41:47 zathras PAM_pwdb[8693]: (sshd) session opened for user
username by (uid=0)
Dec 30 16:42:07 zathras sshd[8693]: log: Packet integrity error (37 != 42)
at channels.c:975
Dec 30 16:42:07 zathras sshd[8693]: fatal: Local: Packet integrity error.
(29)
Dec 30 16:42:07 zathras PAM_pwdb[8693]: (sshd) session closed for user
username

-- 
Rob Russell, Senior Computer Systems Manager  rrussell at cibnetwork.com
Canadian Internet Broadcasting Network    office: (613) 727.4818 x206
Reseau de Diffusion Internet du Canada 	  cel: 282.7885 fax: 727.9366