[syslinux] pxechn.c32 does not do TFTP

[Gene Cumm]

On Fri, Jul 12, 2013 at 10:11 AM, Victor Sudakov <vas at mpeks.tomsk.su> wrote:
> Gene Cumm wrote:
>> >> >
>> >> > I am attempting to chainload a file from TFTP. I have the following
>> >> > lines  in the configuration file:
>> >> >
>> >> > LABEL WDS1
>> >> >  Menu LABEL WDS1
>> >> >  kernel pxechn.c32
>> >> >  append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S
>> >> >
>> >> > The TFTP server at 10.14.141.150 is operational and wdsnbp.com is
>> >> > available at the indicated path. I have tried various combinations of
>> >> > colons, forward and back slashes and URL schemes.
>> >> >
>> >> > However, all i get from pxechn.c32 is
>> >> >
>> >> > pxechn.c32: Attempting to load '10.14.141.150::boot\x86\wdsnbp.com': 2:No such file or directory
>> >> >
>> >> > and it does not even attemt to send any packets to 10.14.141.150 (I
>> >> > checked with WireShark). What I am doing wrong?
>> >>
>> >> What version of PXELINUX?
>> >
>> >  From the syslinux-6.01 distribution. Sorry, should have mentioned
>> > that.

>> > It's from bios/core/pxelinux.0

>> >> Tried just:
>> >>
>> >> LABEL WDS1
>> >>  MENU LABEL WDS1
>> >>  COM32 pxechn.c32
>> >>  APPEND 10.14.141.150::boot\x86\wdsnbp.com -W
>> >
>> > Did it send a packet to 10.14.141.150?
>>
>> Sorry, that was "Have you tried just the following:"
>
> Excuse me, what's the difference between the APPEND line I gave at the
> beginning of my first mail?

The lack of the extra options.

> I certainly remember trying just "APPEND 10.14.141.150::boot\x86\wdsnbp.com"
> without anything good coming out of it.

That I'd expect if it found the file but failed to boot properly since
you forgot "-W".  I'm trying to see if I ever tested with those other
options.

> Hell, I tried various combinations of options, slashes, colons and
> double-colons without any good coming out of it.

> It does load after all, and even prints the error message about
> "2:No such file or directory"
>
> I'm afraid it's trying to find wdsnbp.com locally, as if it did not
> understand that it should TFTP it.

Is it attempting to fetch it from the first TFTP server?  Have you
tried a packet capture on the PXE client's port?

>> What PXE ROM is in use?  An example would be the OROM from an Intel
>> Pro/1000 of a certain version or a Dell Optiplex 760 with BIOS A13
>> (which implies an Intel 82567LM-3 [8086:10de] and a particular ROM
>> version).
>
> I have tried the VirtualBOX's network boot and some Hewlett Packard
> notebook (cannot give more detail at the moment) with the same
> negative result.

Thanks.

--
-Gene