I'm having a problem trying configure an uftp environment.
I'm practicing with the example 1 show in the proxy documentation but I cant get the file go through the proxy server and proxy server it goes directly from uftp server touftp client
Any idea ???
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the case of the "seq out of range" message, this can happen if packets appear out of order, which is common with UDP. Specifically, the client checks if an incoming packet has a sequence number at least 5 less than the most recent packet.
Generally, packets shouldn't be more than 3 out of order, so being out of order by 5 or more could be a symptom of a replay attack. In a test environment however it's unlikely this is the case. You may want to run a Wireshark trace to see what order packets are coming in. You can either modify your router settings to reduce the chance of reordering or you modify MAXMISORDER (defined in client.h) and recompile to change the tolerance of misordered packets.
For the "seq xxx out of cache range" message, this is related to the cache used on the client to write to disk. This can occur under normal operation when there is a burst of dropped packets and the next packet than comes in is has a sequence number at least 5 larger that the last received packet. This is to be expected.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello good afternoon and thanks for help
I'm having a problem trying configure an uftp environment.
I'm practicing with the example 1 show in the proxy documentation but I cant get the file go through the proxy server and proxy server it goes directly from uftp server touftp client
Any idea ???
Hello good morning again.
@bush
Im having some issues yet in the client part log.
When i try to send file from server to client in the client log appears, seq out of range, dropping
any idea for solving this???
Other problem in the log client side is Seq XXXX out of cache range, flushing
Thanks mate
Last edit: Eduardo martinez 2017-05-18
In the case of the "seq out of range" message, this can happen if packets appear out of order, which is common with UDP. Specifically, the client checks if an incoming packet has a sequence number at least 5 less than the most recent packet.
Generally, packets shouldn't be more than 3 out of order, so being out of order by 5 or more could be a symptom of a replay attack. In a test environment however it's unlikely this is the case. You may want to run a Wireshark trace to see what order packets are coming in. You can either modify your router settings to reduce the chance of reordering or you modify MAXMISORDER (defined in client.h) and recompile to change the tolerance of misordered packets.
For the "seq xxx out of cache range" message, this is related to the cache used on the client to write to disk. This can occur under normal operation when there is a burst of dropped packets and the next packet than comes in is has a sequence number at least 5 larger that the last received packet. This is to be expected.
Last edit: Eduardo martinez 2017-05-26