张韡武
2006-Sep-06 15:59 UTC
[syslinux] Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
Hello. In my case I can successfully boot up my Thinkpad X32, but the
same configuration doesn't work for my desktop computer with Intel
network card, with Intel Boot Agent 2.2
DHCP server is 10.0.0.1, tftpd (used tftp-hpa) runs on 10.0.0.32.
netstat told me the daemon listen to 69 UDP port just fine. running tftp
in commandline also shows it works (retrieve pxelinux.0 less then 1
second).
The Thinkpad X32 boots fine (I think their boot code is based on intel
boot agent too), loads Linux kernel fine.
The desktop computer with IBA 2.2 boots, obtain IP address like this:
DHCP Client: 10.0.0.7 MASK: 255.255.255.0 DHCP IP: 10.0.0.32
GATEWAY IP: 10.0.0.1
PXE-E32: TFTP open timeout.
PXE-E32: TFTP open timeout.
PXE-E32: TFTP open timeout.
Note between each of the last 3 error message the computer waited about
one minute before timeout.
I also tried to replace the network card with 3 other cards of the same
model from the same reseller (he only get this brand and this model),
they all behave the same way. This card works fine (e.g. browsing the
web) after installed Windows 98 from CDROM (I don't prefer Windows 98.
The reseller installed Windows 98 to show me this card is OKay).
Any idea how do I go on? Thank you a lot!
Here is my parameter launched tftp-hpa:
# in.tftpd -u nobody -l -vvvvvv -p -c -s /tftpboot/
My dhcp.conf is attached (ISC dhcpd version 3)
-------------- next part --------------
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
# enable dynamic domain name update
ddns-update-style interim;
# ddns key
key updatekey {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret qXv5V0wgDcCO4h+OvAEL3g==;
}
option domain-name "realss";
option domain-name-servers 10.0.0.1;
allow booting;
allow bootp;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = ip-address;
default-lease-time 600000;
max-lease-time 720000;
option subnet-mask 255.255.255.0;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# A slightly different configuration for an internal subnet.
subnet 10.0.0.0 netmask 255.0.0.0{
range 10.0.0.2 10.0.0.32;
option routers 10.0.0.1;
default-lease-time 600000;
max-lease-time 720000;
}
zone realss. {
primary 127.0.0.1;
key updatekey;
}
zone 0.0.10.in-addr.arpa. {
primary 127.0.0.1;
key updatekey;
}
group {
option vendor-class-identifier "PXEClient";
next-server 10.0.0.32;
filename "pxelinux.0";
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
# Zhang Weiwu add this so that we can boot demeter from LAN
host demeter {
hardware ethernet 00:D0:B7:23:33:B9;
fixed-address 10.0.0.7;
# server-name "10.0.0.32";
}
# Zhang Weiwu add this so that we can boot demeter from LAN
host esmeralda {
hardware ethernet 00:11:25:B4:29:87;
fixed-address 10.0.0.250;
}
}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: ???????????
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20060906/b2666dc3/attachment.sig>
张韡武
2006-Sep-07 01:47 UTC
[syslinux] Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
Hello. In my case I can successfully boot up my Thinkpad X32, but the
same configuration doesn't work for my desktop computer with Intel
network card, with Intel Boot Agent 2.2
DHCP server is 10.0.0.1, tftpd (used tftp-hpa) runs on 10.0.0.32.
netstat told me the daemon listen to 69 UDP port just fine. running tftp
in commandline also shows it works (retrieve pxelinux.0 less then 1
second).
The Thinkpad X32 boots fine (I think their boot code is based on intel
boot agent too), loads Linux kernel fine.
The desktop computer with IBA 2.2 boots, obtain IP address like this:
DHCP Client: 10.0.0.7 MASK: 255.255.255.0 DHCP IP: 10.0.0.32
GATEWAY IP: 10.0.0.1
PXE-E32: TFTP open timeout.
PXE-E32: TFTP open timeout.
PXE-E32: TFTP open timeout.
Note between each of the last 3 error message the computer waited about
one minute before timeout.
I also tried to replace the network card with 3 other cards of the same
model from the same reseller (he only get this brand and this model),
they all behave the same way. This card works fine (e.g. browsing the
web) after installed Windows 98 from CDROM (I don't prefer Windows 98.
The reseller installed Windows 98 to show me this card is OKay).
Any idea how do I go on? Thank you a lot!
Here is my parameter launched tftp-hpa:
# in.tftpd -u nobody -l -vvvvvv -p -c -s /tftpboot/
My dhcp.conf is attached (ISC dhcpd version 3)
-------------- next part --------------
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
# enable dynamic domain name update
ddns-update-style interim;
# ddns key
key updatekey {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret qXv5V0wgDcCO4h+OvAEL3g==;
}
option domain-name "realss";
option domain-name-servers 10.0.0.1;
allow booting;
allow bootp;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = ip-address;
default-lease-time 600000;
max-lease-time 720000;
option subnet-mask 255.255.255.0;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# A slightly different configuration for an internal subnet.
subnet 10.0.0.0 netmask 255.0.0.0{
range 10.0.0.2 10.0.0.32;
option routers 10.0.0.1;
default-lease-time 600000;
max-lease-time 720000;
}
zone realss. {
primary 127.0.0.1;
key updatekey;
}
zone 0.0.10.in-addr.arpa. {
primary 127.0.0.1;
key updatekey;
}
group {
option vendor-class-identifier "PXEClient";
next-server 10.0.0.32;
filename "pxelinux.0";
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
# Zhang Weiwu add this so that we can boot demeter from LAN
host demeter {
hardware ethernet 00:D0:B7:23:33:B9;
fixed-address 10.0.0.7;
# server-name "10.0.0.32";
}
# Zhang Weiwu add this so that we can boot demeter from LAN
host esmeralda {
hardware ethernet 00:11:25:B4:29:87;
fixed-address 10.0.0.250;
}
}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: ???????????
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20060907/b9225a85/attachment.sig>
H. Peter Anvin
2006-Sep-08 04:17 UTC
[syslinux] Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
??? wrote:> > The desktop computer with IBA 2.2 boots, obtain IP address like this: > DHCP Client: 10.0.0.7 MASK: 255.255.255.0 DHCP IP: 10.0.0.32 > GATEWAY IP: 10.0.0.1 > PXE-E32: TFTP open timeout. > PXE-E32: TFTP open timeout. > PXE-E32: TFTP open timeout. > > Note between each of the last 3 error message the computer waited about > one minute before timeout. >[...]> group { > option vendor-class-identifier "PXEClient"; > next-server 10.0.0.32; > filename "pxelinux.0"; > option PXE.mtftp-ip 0.0.0.0;^^^^^^^^^^^^^^^^^^^^^^^^^^^> vendor-option-space PXE; >Drop the MTFTP line. -hpa
张韡武
2006-Sep-08 16:37 UTC
[syslinux] Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
? 2006-09-07?? 21:17 -0700?H. Peter Anvin???> > group { > > option vendor-class-identifier "PXEClient"; > > next-server 10.0.0.32; > > filename "pxelinux.0"; > > option PXE.mtftp-ip 0.0.0.0; > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > vendor-option-space PXE; > > > > Drop the MTFTP line.This MTFTP line is borrowed from an article from IBM article "How to install Linux over PXE" http://www-900.ibm.com/developerWorks/cn/linux/l-tip-prompt/l-pex/index.shtml The purpose of that line is to tell the booting machine not to try mtftp (send 0.0.0.0 as mtftp address to client means client should not try mtftp) I also tried to remove that option, the behavior is the same.> > -hpa-- ?????????? http://www.realss.cn Real SoftService http://www.realss.com ????(Sales Department): 0086 592 20 99987 (Chinese, German, English) ????(International Sales): 0086 10 8460 6011 (German and English) ????????????????6? ???????2312??????361005? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: ??????????? URL: <http://www.zytor.com/pipermail/syslinux/attachments/20060909/533b0568/attachment.sig>