net: tftp: Fix incorrect tftp_next_ack on no OACK
authorHarm Berntsen <harm.berntsen@nedap.com>
Fri, 27 Nov 2020 21:45:56 +0000 (21:45 +0000)
committerTom Rini <trini@konsulko.com>
Tue, 19 Jan 2021 14:15:02 +0000 (09:15 -0500)
commitbeb61e13b8134c9aeaf1b2c0a2e13ed71d3be59e
tree06ba542b2ae61abc2320f83530e78053f1c64de8
parent51723c5581241a3886a5adaa780c09138163d0b2
net: tftp: Fix incorrect tftp_next_ack on no OACK

When the tftp server did not send any OACK, the tftp_next_ack variable
was not set to the correct value . As the server was transmitting
blocks we generated a lot of 'Received unexpected block: $n, expected
$n+1' error messages. Depending on the timeout setting the transfer
could still complete though.

Signed-off-by: Harm Berntsen <harm.berntsen@nedap.com>
CC: Ramon Fried <rfried.dev@gmail.com>
Reviewed-By: Ramon Fried <rfried.dev@gmail.com>
net/tftp.c