Re: tftp protocol

[<jscottkasten%yahoo.com@localhost>]

If it is PXE boot, then it's likely a BIOS thing.  Perhaps you can find a BIOS 
update for the hardware?

-S-

--- On Tue, 10/13/09, Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:

> From: Patrick Welche <prlw1%cam.ac.uk@localhost>
> Subject: Re: tftp protocol
> To: "Ignatios Souvatzis" <is%netbsd.org@localhost>
> Cc: tech-net%netbsd.org@localhost
> Date: Tuesday, October 13, 2009, 6:07 AM
> On Mon, Oct 12, 2009 at 09:05:08PM
> +0200, Ignatios Souvatzis wrote:
> > On Mon, Oct 12, 2009 at 06:30:38PM +0100, Patrick
> Welche wrote:
> > > For some reason a tftp client (not netbsd) keeps
> emitting an opcode
> > > of 768 (oddly RFC 768 is UDP) - any idea on how
> an opcode can be > 5?
> > 
> > Yes. 768 is 3*256 - so this is wrong-endian opcode 3,
> a DATA request.
> > Somebody should fix the client, unless you're
> misreading a packet
> > dump. 
> 
> Thank you! (The client is windows vista pxeboot - I'll have
> to put a
> work around in tftpd - makes me wonder what else is
> wrong-endian - tftpd
> server is NetBSD/amd64, client is 32bit vista)
> 
> Patrick
>