[syslinux] Allwell doesn't respond to OACK with ACK in TFTP

Josef Siemes jsiemes at web.de
Mon Feb 4 02:22:08 PST 2002


Neologism <Neologism at POBox.COM> schrieb am 04.02.02:
> I'm trying to network-boot a GCT Allwell set-top box without success. 
> My frustration level is high.
> The problem seems to be that the Allwell is sending a RRQ with an
> option.  tftp-hpa responds with an OACK, and waits for the corresponding
> ACK from the Allwell.  The Allwell never sends that ACK, but instead
> continues with the same RRQ until timeout.
> Having read RFC1782, this makes me think the TFTP client in the Allwell
> is broken.  Ack! Ack ack ack ack ack.  Ack, thpppht.  What do I do?
> The packets follow:
> RRQ:
>     Trivial File Transfer Protocol
>         Opcode: Read Request (1)
>         Source File: pxelinux.0
>         Type: octet
>         Option: blksize = 1456
>     Trivial File Transfer Protocol
>         Opcode: Option Acknowledgement (6)
>         Option: blksize = 1456

Try to tell tftp-hpa not to use the blksize option. Some clients
demand the blksize option, but can't deal with it if the server
accepts it. 

BTW: Maybe the rom sends two RRQ's, since that's the usual behaviour
of some roms (one with blksize, the second one with tsize).

Is it possible to put some network card into this box? Maybe you'll get
better results with some standard card instead the on-board device.



Die Nummer, die sich jeder merkt: Ihre 01212 Wunschrufnummer von WEB.DE! 
Jetzt sichern: http://freemail.web.de

More information about the Syslinux mailing list