Wrong "request-id" in SSH packet when sending over SFTP

[Piotr]

SFTP server: Solarwinds Serv-U 15.1.5.10.
Client: FileZilla 3.29.0

FileZilla sends a constant "request-id" in each packet.
According to RFC ​https://tools.ietf.org/id/draft-ietf-secsh-filexfer-13.txt:

'request-id'

Each request from the client contains a 'request-id' field. Each
response from the server includes that same 'request-id' from the
request that the server is responding to. One possible
implementation is for the client to us a monotonically increasing
request sequence number (modulo 2^{32). There is, however, no
particular requirement the 'request-id' fields be unique.}

The server shows 'request-id' in braces.
Example line as follows:
[30] Fri 24Nov17 09:04:58 - (000015) {0x00000100} SSH_FXP_REALPATH: path: "."

'request-id' is 0x00000100 in this packet. Replay should contains the same number.

The problem is that FileZilla always sends the same 'request-id'. It makes the log analysis very difficult especially that according to the standard, the SFTP commands don't have to be send in the same sequence. I have tried other client software and this behaviour is present only when using FileZilla client.

Attaching:
FileZillaLog.txt: Log from the client, level 4
ServerLog - ClientFileZilla.txt: Full logs of FileZilla's session from the server
ServerLog - ClientWinSCP.txt: Full logs of WinSCP's session from the server as reference of a good session.

I'm not considering this behaviour as a bug since standard says it is not a mandatory to have an unique id, however it is very important feature request for troubleshooting purposes.

[Tim Kosse]

There is, however, no particular requirement the 'request-id' fields be unique.