[syslinux] ethereal log of PXE bootup

[Ed Sutter]

H. Peter Anvin wrote:

> Ed Sutter wrote:
> 
>>
>> This maybe outside the context of this list, but I'll shoot it out
>> anyway...
>>
>> I've looked at a few ethereal dumps of PXE transactions and I noticed
>> that the client adds the "tsize" option to the TFTP read request (as 
>> expected), and the server responds (also as expected), but in more 
>> than one case I notice that the client then returns  a TFTP_ERROR, 
>> apparently indicating that it doesn't understand the TFTP_OACK 
>> response that the server sent in response to the 'tsize' request.
>>
>> Everything seems to work, but the client sends this error.  Seems 
>> kinda strange that the client wouldn't understand the TFTP_OACK, since 
>> it was the device that generated the 'tsize' request in the first place.
>>
> 
> It looks strange, but what the client is saying here really is "thanks, 
> that's all I wanted to know."
> 
Ok.
My guess is that this is used to make some TFTP servers happy...
By generating the error from the client, the server receives the error and
closes that RRQ transaction/session.  This allows the client to send
another RRQ after it has received information about the incoming file size.
Regardless, as long as it's expected, it works for me.
Thanks.
Ed

BTW... I was able to successfully serve a PXELinux client.  Very simple
case, but it's a start!