thr3ads.net - Syslinux - [syslinux] PXELinux can't load the config file? [Mar 2003]

If this information is useful, please help other people find it:
Share via:

Ciprian Paunescu

2003-Mar-21 02:50 UTC

[syslinux] PXELinux can't load the config file?

Hi,

I am working on a cluster of PCs, and I want to
boot them from an SGI IRIX machine.
The PCs use Supermicro XEON MB, with dual GigE built in.
They have Intel Boot Agent GE v 1.1.09 and PXE 2.1 (083).

I have DHCP and TFTP on the IRIX machine, pxelinux.0
loads, but it can't load the configuration file?
tftp on the host tries to send the file, but data
transfers do not receive ACKs.
I got tftp-hpa to compile on the IRIX box, but it doesn't 
work any better. Any ideeas on what is wrong, and
how can I fix it?

I "snooped" on the nework, and here's what I see:
192.168.1.1 is the server, 192.168.1.4 the client

This listing uses the SGI tftp, the data packet doesn't
get ACK, this sequence keeps repeating:

_______________________
ETHER:  ----- Ether Header -----
ETHER:
ETHER:  Packet 56 arrived at 17:55:19.66
ETHER:  Packet size = 80 bytes
ETHER:  Destination = ff:ff:ff:ff:ff:ff, (broadcast)
ETHER:  Source      = 0:30:48:27:77:c6,
ETHER:  Ethertype = 0800 (IP)
ETHER:
IP:   ----- IP Header -----
IP:
IP:   Version = 4
IP:   Header length = 20 bytes
IP:   Type of service = 0x00
IP:         xxx. .... = 0 (precedence)
IP:         ...0 .... = normal delay
IP:         .... 0... = normal throughput
IP:         .... .0.. = normal reliability
IP:   Total length = 66 bytes
IP:   Identification = 29
IP:   Flags = 0x0
IP:         .0.. .... = may fragment
IP:         ..0. .... = last fragment
IP:   Fragment offset = 0 bytes
IP:   Time to live = 20 seconds/hops
IP:   Protocol = 17 (UDP)
IP:   Header checksum = e4e2
IP:   Source address = 192.168.1.4, 192.168.1.4
IP:   Destination address = 0.0.0.0, OLD-BROADCAST
IP:   No options
IP:
UDP:  ----- UDP Header -----
UDP:
UDP:  Source port = 57217
UDP:  Destination port = 69 (TFTP)
UDP:  Length = 46
UDP:  Checksum = 4CEB
UDP:
TFTP:  ----- Trivial File Transfer Protocol -----
TFTP:
TFTP:  Opcode = 1 (read request)
TFTP:  File name = "pxelinux.cfg/C0A80104"
TFTP:  Transfer mode = octet

ETHER:  ----- Ether Header -----
ETHER:
ETHER:  Packet 57 arrived at 17:55:19.66
ETHER:  Packet size = 560 bytes
ETHER:  Destination = 0:30:48:27:77:c6,
ETHER:  Source      = 8:0:69:10:2b:fd, SGI
ETHER:  Ethertype = 0800 (IP)
ETHER:
IP:   ----- IP Header -----
IP:
IP:   Version = 4
IP:   Header length = 20 bytes
IP:   Type of service = 0x00
IP:         xxx. .... = 0 (precedence)
IP:         ...0 .... = normal delay
IP:         .... 0... = normal throughput
IP:         .... .0.. = normal reliability
IP:   Total length = 544 bytes
IP:   Identification = 46012
IP:   Flags = 0x0
IP:         .0.. .... = may fragment
IP:         ..0. .... = last fragment
IP:   Fragment offset = 0 bytes
IP:   Time to live = 60 seconds/hops
IP:   Protocol = 17 (UDP)
IP:   Header checksum = 45bb
IP:   Source address = 192.168.1.1, raschal-wink
IP:   Destination address = 192.168.1.4, 192.168.1.4
IP:   No options
IP:  
UDP:  ----- UDP Header -----
UDP: 
UDP:  Source port = 1363
UDP:  Destination port = 57217
UDP:  Length = 524
UDP:  Checksum = 2048
UDP: 
TFTP:  ----- Trivial File Transfer Protocol -----
TFTP: 
TFTP:  Opcode = 3 (data packet)
TFTP:  Data block = 1
TFTP:  [ 512 bytes of data ]

_____________________________________

And here's the same problem using the tftp-hpa 
implementation.
This time I get an "Opcode 6?" error

_____________________________________
ETHER:  ----- Ether Header -----
ETHER:
ETHER:  Packet 30 arrived at 18:37:47.87
ETHER:  Packet size = 80 bytes
ETHER:  Destination = ff:ff:ff:ff:ff:ff, (broadcast)
ETHER:  Source      = 0:30:48:27:77:c6,
ETHER:  Ethertype = 0800 (IP)
ETHER:
IP:   ----- IP Header -----
IP:
IP:   Version = 4
IP:   Header length = 20 bytes
IP:   Type of service = 0x00
IP:         xxx. .... = 0 (precedence)
IP:         ...0 .... = normal delay
IP:         .... 0... = normal throughput
IP:         .... .0.. = normal reliability
IP:   Total length = 66 bytes
IP:   Identification = 16
IP:   Flags = 0x0
IP:         .0.. .... = may fragment
IP:         ..0. .... = last fragment
IP:   Fragment offset = 0 bytes
IP:   Time to live = 20 seconds/hops
IP:   Protocol = 17 (UDP)
IP:   Header checksum = e4ef
IP:   Source address = 192.168.1.4, 192.168.1.4
IP:   Destination address = 0.0.0.0, OLD-BROADCAST
IP:   No options
IP:
UDP:  ----- UDP Header -----
UDP:
UDP:  Source port = 57217
UDP:  Destination port = 69 (TFTP)
UDP:  Length = 46
UDP:  Checksum = 4CEB
UDP:
TFTP:  ----- Trivial File Transfer Protocol -----
TFTP:
TFTP:  Opcode = 1 (read request)
TFTP:  File name = "pxelinux.cfg/C0A80104"
TFTP:  Transfer mode = octet

ETHER:  ----- Ether Header -----
ETHER:
ETHER:  Packet 31 arrived at 18:37:47.87
ETHER:  Packet size = 56 bytes
ETHER:  Destination = 0:30:48:27:77:c6,
ETHER:  Source      = 8:0:69:10:2b:fd, SGI
ETHER:  Ethertype = 0800 (IP)
ETHER:
IP:   ----- IP Header -----
IP:
IP:   Version = 4
IP:   Header length = 20 bytes
IP:   Type of service = 0x00
IP:         xxx. .... = 0 (precedence)
IP:         ...0 .... = normal delay
IP:         .... 0... = normal throughput
IP:         .... .0.. = normal reliability
IP:   Total length = 40 bytes
IP:   Identification = 49434
IP:   Flags = 0x0
IP:         .0.. .... = may fragment
IP:         ..0. .... = last fragment
IP:   Fragment offset = 0 bytes
IP:   Time to live = 60 seconds/hops
IP:   Protocol = 17 (UDP)
IP:   Header checksum = 3a55
IP:   Source address = 192.168.1.1, raschal-wink
IP:   Destination address = 192.168.1.4, 192.168.1.4
IP:   No options
IP:  
UDP:  ----- UDP Header -----
UDP: 
UDP:  Source port = 1386
UDP:  Destination port = 57217
UDP:  Length = 20
UDP:  Checksum = 1E50
UDP: 
TFTP:  ----- Trivial File Transfer Protocol -----
TFTP: 
TFTP:  Opcode = 6 (?)



------------------------------
K Free E-mail http://www.k.ro/
Cumpara online de la METRO prin http://www.shift.ro/

H. Peter Anvin

2003-Mar-21 04:03 UTC

head link

[syslinux] PXELinux can't load the config file?

Ciprian Paunescu wrote:> Hi,
> 
> I am working on a cluster of PCs, and I want to
> boot them from an SGI IRIX machine.
> The PCs use Supermicro XEON MB, with dual GigE built in.
> They have Intel Boot Agent GE v 1.1.09 and PXE 2.1 (083).
> 
> I have DHCP and TFTP on the IRIX machine, pxelinux.0
> loads, but it can't load the configuration file?
> tftp on the host tries to send the file, but data
> transfers do not receive ACKs.
> I got tftp-hpa to compile on the IRIX box, but it doesn't 
> work any better. Any ideeas on what is wrong, and
> how can I fix it?
Looks like the PXE stack has a problem with UDP receive -- the transmit
side obviously works.  I would hunt for a firmware upgrade; it sounds
like they have some pretty ancient PXE stack.

	-hpa

Josef Siemes

2003-Mar-21 10:23 UTC

head link

[syslinux] PXELinux can't load the config file?

Hi,

Ciprian Paunescu <cip at k.ro> schrieb am 21.03.03
04:01:36:> I am working on a cluster of PCs, and I want to
> boot them from an SGI IRIX machine.
> The PCs use Supermicro XEON MB, with dual GigE built in.
> They have Intel Boot Agent GE v 1.1.09 and PXE 2.1 (083).
> 
> I have DHCP and TFTP on the IRIX machine, pxelinux.0
> loads, but it can't load the configuration file?
> tftp on the host tries to send the file, but data
> transfers do not receive ACKs.
I doubt that SGI's tftp server implements the tsize option, which
pxelinux needs. So even on a linux box with this tftp server you
won't be able to boot anyway.
> I got tftp-hpa to compile on the IRIX box, but it doesn't 
> work any better. Any ideeas on what is wrong, and
> how can I fix it?
The dumps are to few for that. Give a hex dump of the
TFTP request, and a hex dump of the server's response
with the tsize option (first 100 bytes should be enough,
though ...). Perhaps the server doesn't give 
the correct size to the client.
> I "snooped" on the nework, and here's what I see:
> 192.168.1.1 is the server, 192.168.1.4 the client
> And here's the same problem using the tftp-hpa 
> implementation.
> This time I get an "Opcode 6?" error
'Opcode 6' is the 'OACK' Option (Option Acknowledgement),
so this seems correct.

BTW: Could you put some standard network card into the
client to test if it's the PXE rom to blame? A recent Intel
Pro/100 with MBA >=2  would be nice. I also have seen the
Pro/1000 boot without problems.

Regards,

Josef



______________________________________________________________________________
Jetzt 52 verschiedene Briefpapiere f?r Ihre E-Mails bei
WEB.DE FreeMail - http://freemail.web.de/features/?mc=021140

Maybe Matching Threads

Search for more maybe matching threads

Syslinux - Mar 2003 - PXELinux can't load the config file?

[syslinux] PXELinux can't load the config file?

[syslinux] PXELinux can't load the config file?

[syslinux] PXELinux can't load the config file?

Maybe Matching Threads