[ipxe-devel] [gPXE] nomenclature to use...

carlyoung at keycomm.co.uk carlyoung at keycomm.co.uk
Tue Nov 9 12:59:14 UTC 2010

 On Mon 08/11/10 6:09 PM , Shao Miller Shao.Miller at yrdsb.edu.on.ca
   carlyoung at keycomm.co.uk wrote:  Hi all.
 ... ... ...
 I know this NIC. :) It's the (previously NetXen) QLogic "Phantom"
 This has apparently been shipped with a "gPXE" client and I am
having some interoperability problems with a PXE boot server in that
the client sends a boot request with an empty boot filename despite
the DHCP ack containing a filename (for TFTP access).
 Can you capture the DHCP transaction with Wireshark or 'tcpdump' and
filter it for DHCP and share the resulting packets as an e-mail
attachment? I don't quite understand what you mean by the client
sending an empty boot filename. Do you mean it makes a TFTP request
with an empty filename? If so, do you have a Control-B CLI? If so,
can you please try:
 dhcp net0
 show filename
 and report whether or not you got a filename from the DHCP service?
	Thanks Shao, 

	I have attached gpxe.cap. You can see the DHCP ACK in frame 14 with
a boot file name present and frame 15 shows a TFTP read with an empty
filename.  I managed to find out version of gPXE client this morning -
apparently it is 0.9.9 embedded. 

	I can't do the CLI operations currently - I will have to ask for
those to be performed on my behalf. 

	I just want to know if I should be looking at getting the gPXE
client 'fixed' or the server or what... 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20101109/e376d837/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpxe.cap
Type: application/octet-stream
Size: 18577 bytes
Desc: not available
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20101109/e376d837/attachment.obj>

More information about the ipxe-devel mailing list