[syslinux] Re: Problems with PXE booting linux

[Geert Stappers]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Oct 22, 2005 at 03:27:57PM -0700, Steve Waldbusser wrote:
> On 10/22/2005 5:48 AM, Geert Stappers wrote:
> >On Wed, Oct 19, 2005 at 11:28:52PM -0700, Steve Waldbusser wrote:
> > 

  <snip/>

> >>P.S. For what it's worth, here's a tcpdump log of the DHCP sequence. 
> >>   
> >Why only the DHCP sequence?  ( Please extend the tcpdump filter )
> > 
> Here it is. It's not too long to paste inline:
> # tcpdump -s 1500 ether host 0:1:29:f8:c6:cc
> tcpdump: listening on eth0
> 13:35:33.047374 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x2907d651 
> vend-rfc1048 DHCP:DISCOVER MSZ:1500 
> VC:69.116.104.101.114.98.111.111.116.45.53.46.52 PR:SM+DG+HN+VO 
> T150:175.5.1.16.236.129.105.177.2.3.013:35:33.048103 192.168.1.10.bootps 
> > 192.168.1.50.bootpc:  xid:0x2907d651 Y:192.168.1.50 S:192.168.1.10 
> file "pxelinux.0" vend-rfc1048 DHCP:OFFER SID:192.168.1.10 LT:43200 
> SM:255.255.255.0 DG:192.168.1.1 VO:1.4.0.0.0.0 [tos 0x10]

 <snip> hard to read output of tcpdump </snip>

Yes, it is short, but providing tcpdump output in libpcap format 
on a website has has other advantages then just being not too long ...

> 13:35:37.296350 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
> 13:35:37.296837 192.168.1.10.4166 > 192.168.1.50.2001:  udp 264
> 13:35:37.296948 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
> 13:35:42.283930 arp who-has 192.168.1.50 tell 192.168.1.10
> 13:35:43.283929 arp who-has 192.168.1.50 tell 192.168.1.10
> 13:35:44.284639 arp who-has 192.168.1.50 tell 192.168.1.10
> 
> 
> The udp packets are the successful TFTP transfer of the 13148 byte 
> pxelinux.0 file. That's followed by arp requests unanswered by the DFI 
> board (192.168.1.50) which is further confirmation that it is locked hard.

Could it be that the pxelinux.0 is maformed?
( corrupted by a ftp client doing crlf/lf transformations ??? )

Try another pxelinux.0 and report your progress

> >>This is followed by an uneventful TFTP transfer of pxelinux.0 and then 
> >>complete silence:
> >>
> >>17:33:50.469078 DHCP:DISCOVER
> >>17:33:50.469868 DHCP:OFFER 
> >>17:33:55.026454 DHCP:REQUEST
> >>17:33:55.027280 DHCP:ACK 
> >>   
> >
> >It is the tcpdump filter that "creates" the complete silence ???
> >
> No, the filter is based on the ethernet address so it's not dropping 
> anything it shouldn't.

Meanwhile I have a more clear picture of what is happening at your end.

> Thanks,
> Steve


GSt

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDW0mKOSINbgwa/7sRAp0CAKClLkoyQ5BILuBRKnIxwyLxzT0GPACgpw/E
CkO9HlLjknXvjUcMqZEZs4U=
=GSCR
-----END PGP SIGNATURE-----