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. > > > >> Which variant, pxelinux.0 or lpxelinux.0? > > > > pxelinux.0 > > > >> If 6.xx, which architecture? > > > It's from bios/core/pxelinux.0 > > BIOS is the answer.I see.> > >> 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? I certainly remember trying just "APPEND 10.14.141.150::boot\x86\wdsnbp.com" without anything good coming out of it. Hell, I tried various combinations of options, slashes, colons and double-colons without any good coming out of it.> >> I also notice I dropped the double colon in the docs. > > > > Why did you write "COM32 pxechn.c32" and not "KERNEL pxechn.c32" Does > > it make any difference? > > It should not. COM32 is just more explicit. KERNEL needs to guess > what to load it as. > > > I have also noticed that the syslinux-6.01.tar.gz contains several > > variants of pxechn.c32, may I be using the wrong one? > > > > bios/com32/modules/pxechn.c32 > > efi32/com32/modules/pxechn.c32 > > efi64/com32/modules/pxechn.c32 > > Herein lies the different architectures. Did you use > bios/com32/modules/pxechn.c32 with bios/core/pxelinux.0 ?Yes, I did $ cmp syslinux-6.01/bios/com32/modules/pxechn.c32 /tftpboot/pxechn.c32 $ 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.> > > 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. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov at sibptus.tomsk.ru
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
Gene Cumm wrote: [dd]> >> >> > >> >> 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.Should not it attempt to TFTP-download boot\x86\wdsnbp.com from 10.14.141.150 regardless of any options? Can you perhaps try to reproduce my setup and see if pxechn.c32 sends any traffic at all to the TFTP server?> > 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.I will be able to do more testing on Monday when I am back at work. If you want me to test "APPEND 10.14.141.150::boot\x86\wdsnbp.com -W" I certainly will.> > 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?The pxelinux.0 itself is not at 10.14.141.150, it's on a different TFTP server. In fact, I boot it like this: ! ip dhcp pool EVERYONE network 10.14.140.0 255.255.254.0 bootfile pxelinux.0 next-server 10.14.140.126 default-router 10.14.141.254 dns-server 10.14.140.125 10.14.140.5 domain-name sibptus.transneft.ru netbios-node-type h-node netbios-name-server 10.14.134.1 10.14.134.4 option 42 ip 10.14.129.71 10.14.140.125 lease 30 !> Have you tried a packet capture on the PXE client's port?No, that would not have been very easy technically. I have only tried a packet capture at 10.14.141.150 and have not seen a single packet from the PXE client. On Monday, I will perhaps setup a port monitoring session on the Catalyst and try a capture on the PXE client's port (where the HP notebook is). -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov at sibptus.tomsk.ru