[syslinux] Re: Problems with PXE booting linux

Steve Waldbusser waldbusser at nextbeacon.com
Sat Oct 22 15:27:57 PDT 2005


On 10/22/2005 5:48 AM, Geert Stappers wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Wed, Oct 19, 2005 at 11:28:52PM -0700, Steve Waldbusser wrote:
>  
>
>>I still haven't solved this problem and I've search the archives 
>>extensively with no clue. Here is a more complete boot screen:
>>
>>PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin
>>    
>>
>   <snip/>
>  
>
>>This is a DFI 855GME-MGF board, with r8169 on-board ethernet
>>Etherboot 5.4.1 is run from a DOS floppy
>>Does anyone have any ideas about what the problem is?
>>
>>Thanks,
>>Steve
>>
>>
>>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]
13:35:37.275268 192.168.1.50.bootpc > 255.255.255.255.bootps:  
xid:0x2907d651 vend-rfc1048 DHCP:REQUEST SID:192.168.1.10 
RQ:192.168.1.50 MSZ:1500 
VC:69.116.104.101.114.98.111.111.116.45.53.46.52 
PR:SM+DG+HN+VO+RP+T-128+T-127+T-126+T-106 
T150:175.5.1.16.236.129.105.177.2.3.0
13:35:37.276045 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:ACK 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]
13:35:37.280126 arp who-has 192.168.1.10 tell 192.168.1.50
13:35:37.280160 arp reply 192.168.1.10 is-at 0:a0:cc:d6:d9:a0
13:35:37.280223 192.168.1.50.2001 > 192.168.1.10.tftp:  32 RRQ "pxelinux.0"
13:35:37.290269 192.168.1.10.4166 > 192.168.1.50.2001:  udp 15
13:35:37.290349 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.290785 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.291106 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.291656 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.291980 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.292154 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.292465 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.292962 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.293273 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.293427 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.293738 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.294242 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.294561 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.294719 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.295035 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.295521 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
13:35:37.295829 192.168.1.50.2001 > 192.168.1.10.4166:  udp 4
13:35:37.296038 192.168.1.10.4166 > 192.168.1.50.2001:  udp 1436
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.

>  
>
>>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.


Thanks,
Steve

>
>GSt
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFDWjUOOSINbgwa/7sRAvyuAKCHb4VzkxQzd5ajVVYClhbP9jVIewCghKHQ
>dN2pOE9NRIOf1zitF/rSiXY=
>=Ca6Q
>-----END PGP SIGNATURE-----
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX at zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>
>
>  
>





More information about the Syslinux mailing list