mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-10 23:24:38 +00:00
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>
This commit is contained in:
parent
51723c5581
commit
beb61e13b8
1 changed files with 3 additions and 1 deletions
|
@ -630,8 +630,10 @@ static void tftp_handler(uchar *pkt, unsigned dest, struct in_addr sip,
|
|||
tftp_cur_block++;
|
||||
tftp_cur_block %= TFTP_SEQUENCE_SIZE;
|
||||
|
||||
if (tftp_state == STATE_SEND_RRQ)
|
||||
if (tftp_state == STATE_SEND_RRQ) {
|
||||
debug("Server did not acknowledge any options!\n");
|
||||
tftp_next_ack = tftp_windowsize;
|
||||
}
|
||||
|
||||
if (tftp_state == STATE_SEND_RRQ || tftp_state == STATE_OACK ||
|
||||
tftp_state == STATE_RECV_WRQ) {
|
||||
|
|
Loading…
Reference in a new issue