[syslinux] pxechn.c32 does not do TFTP
Victor Sudakov
vas at mpeks.tomsk.su
Fri Jul 12 08:31:38 PDT 2013
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
More information about the Syslinux
mailing list