| commit | 1cb1a66aed921060fa34d161b52e95d05de18ec1 | |
| author | Milan Plzik <milan.plzik@gmail.com> | |
| Thu, 7 Jan 2010 12:39:43 +0000 (7 13:39 +0100) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Wed, 13 Jan 2010 23:14:16 +0000 (13 17:14 -0600) | ||
| tree | a279471075a9598bf03e1ab901788a2756171d7a | treesnapshot (tar.gz zip) |
| parent | bb0300dc57c10b3721451b0ff566a03f9276cc77 | commitdiff |
Qemu's internal TFTP server breaks lock-step-iness of TFTP
According to RFC 1350 and RFC 2347, TFTP server should answer RRQ by
either OACK or DATA packet. Qemu's internal TFTP server answers RRQ with
additional options by sending both OACK and DATA packet, thus breaking
the "lock-step" feature of the protocol, and also confuses client.
Proposed solution would be to, in case of OACK packet, wait for ACK
from client and just then start sending data. Attached patch implements
this.
Signed-off-by: Thomas Horsten <thomas@horsten.com>
Signed-off-by: Milan Plzik <milan.plzik@gmail.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
According to RFC 1350 and RFC 2347, TFTP server should answer RRQ by
either OACK or DATA packet. Qemu's internal TFTP server answers RRQ with
additional options by sending both OACK and DATA packet, thus breaking
the "lock-step" feature of the protocol, and also confuses client.
Proposed solution would be to, in case of OACK packet, wait for ACK
from client and just then start sending data. Attached patch implements
this.
Signed-off-by: Thomas Horsten <thomas@horsten.com>
Signed-off-by: Milan Plzik <milan.plzik@gmail.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
| slirp/tftp.c | diffblobblamehistory |