On Tuesday 02 August 2011 15:25:31 you wrote: > Hi Andreas, > > Thanks for your time and answers. Attached you will find a full debug log of > the problem, as requested. If you need additional logging or data, please > let me know. > > I agree with you that even if the packet size of 32000 might not be as per > specifications, it most likely won't be the cause of problem I'm facing > here. Is this something that should be corrected on the server side? > Because I do think it may eventually lead to problems as some of the data > packets that we receive from the server could easily exceed 64k bytes.
Please test: http://cpaste.org/1228/ I've looked at the output of openssh. They use 0 as the first window and let it grow. > Right now we are just using ssh_channel_write() (of course after we have > logged in and called ssh_channel_new() and ssh_channel_open_session()). > Knowing that I am connecting to a 'plain' SSH server that I can connect to > using the OS ssh command as well, I was thinking that I could try that > approach with our client program too. Hence my question if using the > ssh_channel_request_exec() function as a way of issuing commands to the > server (instead of the ssh_channel_write() function) might yield different > results. Normall you need a non-interactive shell: http://api.libssh.org/master/libssh_tutor_shell.html or use the exec command: http://api.libssh.org/master/libssh_tutor_command.html Cheers, -- andreas -- Andreas Schneider GPG-ID: F33E3FC6 www.cryptomilk.org [email protected]
