Syslinux - Oct 2004 - Intel Boot Agent 1.2.16 specific problem

Hello,

I have a currently working pxe/tftp network boot configuration. I'm 
using tftpd-hpa.

Recently I tried to add a new PC, which has an onboard Intel 82540 GigE 
ethernet controller. When the PC boots, it successfully speaks with DNS 
and attempts to download pxelinux.0 from the tftp server. This ends in a 
TFTPD read time out. I tcpdumped the traffic and found:


192.168.13.167.2070 > 192.168.12.22.69:  27 RRQ "pxelinux.0"
192.168.12.22.34484 > 192.168.13.167.2070:  udp 14
192.168.13.167.3651 > 192.168.12.22.34484:  udp 17
192.168.12.22 > 192.168.13.167: icmp: 192.168.12.22 udp port 34484 
unreachable [tos 0xc0]

192.168.13.167.2071 > 192.168.12.22.69:  32 RRQ "pxelinux.0"
192.168.12.22.34485 > 192.168.13.167.2071:  udp 516
192.168.13.167.3651 > 192.168.12.22.34485:  udp 4
192.168.12.22 > 192.168.13.167: icmp: 192.168.12.22 udp port 34485 
unreachable [tos 0xc0]

It seems like the tfp machine is unhappy about the PC changing source 
ports. Has anyone seen this before? Or have suggestions for a work around?

Thanks in advance,
matthias

Matthias Halfmann wrote:
> Hello,
> 
> I have a currently working pxe/tftp network boot configuration. I'm 
> using tftpd-hpa.
> 
> Recently I tried to add a new PC, which has an onboard Intel 82540 GigE 
> ethernet controller. When the PC boots, it successfully speaks with DNS 
> and attempts to download pxelinux.0 from the tftp server. This ends in a 
> TFTPD read time out. I tcpdumped the traffic and found:
> 
> 
> 192.168.13.167.2070 > 192.168.12.22.69:  27 RRQ "pxelinux.0"
> 192.168.12.22.34484 > 192.168.13.167.2070:  udp 14
> 192.168.13.167.3651 > 192.168.12.22.34484:  udp 17
> 192.168.12.22 > 192.168.13.167: icmp: 192.168.12.22 udp port 34484 
> unreachable [tos 0xc0]
> 
> 192.168.13.167.2071 > 192.168.12.22.69:  32 RRQ "pxelinux.0"
> 192.168.12.22.34485 > 192.168.13.167.2071:  udp 516
> 192.168.13.167.3651 > 192.168.12.22.34485:  udp 4
> 192.168.12.22 > 192.168.13.167: icmp: 192.168.12.22 udp port 34485 
> unreachable [tos 0xc0]
> 
> It seems like the tfp machine is unhappy about the PC changing source 
> ports. Has anyone seen this before? Or have suggestions for a work around?
> 
That's a serious bug, and a total violation of the TFTP protocol.

	-hpa