Pratik Pawar (Customer) asked a question.
Bad length (32796) for cmd=SSH_MSG_CHANNEL_DATA - max. allowed=32768
Receiving above error from server for client version:
- SSH-2.0-WS_FTP-12.7.0-0
- SSH-2.0-WS_FTP-12.8.0-0
- SSH-2.0-WS_FTP-12.6.0-0
Is there a way to configure channel length on WS FTP SFTP client or WS_FTP sends 28 additional bytes for specific client use case?
@Pratik Pawar (Customer) Please follow the KB: https://community.progress.com/s/article/Received-too-large-2999993-SFTP-Packet-Max-supported-packet-size-is-1024000B
Also apply section 1 of KB https://community.progress.com/s/article/Error-0-reading-SSH-packet-size-block
See if these helps.
If issue persists, then open a case with WSFTP technical Support and we shall advise further.
Hi @Samik Chakraborty (Progress Software Development) I am experiencing issue with WS FTP Pro client. FTP client isn't respecting set server limits and sending more bytes of data over the channel. Server does advertise SSH_MSG_CHANNEL_DATA/ServerMaxPacket limits with client at the time of the connection negotiations.
PFA: debug logs
https://datatracker.ietf.org/doc/html/rfc4254#section-5.2
Related to https://community.progress.com/s/question/0D54Q00007oKeLcSAK/error-842c0000
I applied all MTU and TCP scaling changes as recommended on above ticket per RFC-1323 to no avail.
@Pratik Pawar (Customer) Please submit a case via the Portal and we shall try to provide a Workaround for the reported issue.
Hi Samik, it appears that WS FTP is not handling buffer calculations when file-handle is of size more than 4 bytes. For file handle sizes more than 4; WS FTP just sends those additional bytes on SSH_MSG_CHANNEL_DATA; causing the failures.
File handle for channels could be up to 256 bytes per RFC.
I don't have the support account to raise the ticket. I will see if it can be done.
We are experiencing the same problem. Are there any updates on this topic or maybe even a solution?
Are you experiencing it with WS SFTP Server or client? Whats the server you are using?
It is the WS_SFTP client we are having problems with..
Whats the server you are using?