By looking at the network packets, I can verify that the client does not get any filename from the DHCP server.
Could this be related to a buggy or old PXE v0.99j ? My DHCP server is of version isc-dhcpd-V3.0.1rc13.
H. Hallingstad
Em Sáb, 2004-09-11 às 12:39, Håkon Hallingstad escreveu:Hi,
I have problems with the initial DHCP connection and would appreciate any help.
The client has a 3c905B-TX NIC and Managed Boot Agent (MBA) set to PXE. When booting the client, it waits about one minute at the "DHCP.." prompt, before it finally gives up:
PXE-E53: No boot filename received from BINL, DHCP, or BOOTP
The server has the DHCP server up and running, and seems to respond to client's DHCP requests:
$ tail -f /var/log/messages Sep 11 09:33:28 dirac dhcpd: DHCPDISCOVER from 00:50:04:9e:55:4a via eth0 Sep 11 09:33:29 dirac dhcpd: DHCPOFFER on 192.168.1.5 to 00:50:04:9e:55:4a via eth0 Sep 11 09:33:29 dirac dhcpd: DHCPREQUEST for 192.168.1.5 (192.168.1.1) from 00:50:04:9e:55:4a via eth0 Sep 11 09:33:29 dirac dhcpd: DHCPACK on 192.168.1.5 to 00:50:04:9e:55:4a via eth0 Sep 11 09:33:35 dirac dhcpd: DHCPDISCOVER from 00:50:04:9e:55:4a via eth0 Sep 11 09:33:35 dirac dhcpd: DHCPOFFER on 192.168.1.5 to 00:50:04:9e:55:4a via eth0 Sep 11 09:33:51 dirac dhcpd: DHCPDISCOVER from 00:50:04:9e:55:4a via eth0 Sep 11 09:33:51 dirac dhcpd: DHCPOFFER on 192.168.1.5 to 00:50:04:9e:55:4a via eth0
$ tcpdump -i eth0 13:38:01.235367 04:9e:55:4a:00:50 sap 4a > 10:00:00:00:00:50 sap 55 I (s=0,r=0,C) len=42 13:38:09.838450 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:04:9e:55:4a, length: 548 13:38:09.838886 IP dirac.localdomain > maxwell: icmp 28: echo request seq 0 13:38:10.000275 IP dirac.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300 13:38:10.005634 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:04:9e:55:4a, length: 548 13:38:10.081488 IP dirac.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300 13:38:14.837477 arp who-has maxwell tell dirac.localdomain 13:38:14.837566 arp reply maxwell is-at 00:50:04:9e:55:4a 13:38:17.722692 IP maxwell.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:04:9e:55:4a, length: 548 13:38:17.723040 IP dirac.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300 13:38:33.536595 IP maxwell.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:04:9e:55:4a, length: 548 13:38:33.536951 IP dirac.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300
iptables does not block any outbound traffic. I have tried different configurations for the DHCP server, for instance
subnet 192.168.1.0 netmask 255.255.255.0 { option routers 192.168.1.1; option broadcast-address 192.168.1.255; host maxwell { option root-path "192.168.1.1:/usr/local/share/ltsp/i386"; hardware ethernet 04:9e:55:4a:00:50; fixed-address 192.168.1.5; filename "/lts/2.4.26-ltsp-2/pxelinux.0"; } }
The tftp daemon is set up with chroot jail, and listening on *:tftp.
H. Hallingstad
