Daniel Prevett <[EMAIL PROTECTED]> writes:
> When uploading a file to an FTP server through lsh 0.9.13, the upload
> stalls and eventually has to be cancelled. When the transfer is
> cancelled, the file left on the server is either truncated or empty (if
> it is a small file). This is pure conjecture on my part, but perhaps a
> buffer is not getting emptied?
Could be the case. Or it may be a flow control problem.
> I believe that this problem is with lsh as SEcureFX functions with OpenSSH
> and the Data Fellows / F-Secure / SSH Communications servers.
>
> I'd be glad to provide any other information about this.
I don't quite understand your setup... From your description, I
imagine its something like
1. A specialized ftp-like client, whick talks to
2. lsh, which connects to a remote
3. lshd (or are you using openssh's sshd or ssh2d at the other end?)
which sets up a tcp tunnel in each direction, which are used for
talking to
4. some remote plain ftp server.
I probably have some details wrong here. Please correct them. In
particular, I would need to know the command line passed to lsh and/or
lshd, what the setup at the end of the tunnel is (ssh server software,
if any extra programs are exec:ed besides the port forwarding), in
which directions the tunnels are established (i.e. if you're using
active or passive ftp, although I never remember which mode is which
;-), any diagnostic messages from lsh (preferably in --verbose or even
--verbose --trace mode).
I'm not at all familiar with SecureFX.
You can also try running both lsh and lshd with the --debug flag. That
should dump all sent and received packets, which should help figuring
out where on the way the file contents was lost.
Regards,
/Niels
