1.pls update syslinux
2. add retry
3.pls add function：
pls check :
and find this part:
Option 208 pxelinux.magic
Earlier versions of PXELINUX required this option to be set to F1:00:74:7E (241.0.116.126)
for PXELINUX to be able to recognize any special DHCP options whatsoever. As of PXELINUX 3.55, this option is deprecated and is no longer required.
Option 209 pxelinux.configfile
Specify the initial PXELINUX configuration file name, which may be qualified or unqualified.
Option 210 pxelinux.pathprefix
Specify the PXELINUX common path prefix, instead of deriving it from the boot file name. This almost certainly needs to end in whatever character the TFTP server OS uses as apathname separator
, e.g. slash (/) for Unix.
Option 211 pxelinux.reboottime
Specify, in seconds, the time to wait before reboot in the event of TFTP failure. "0" (zero)
means wait "forever" (in reality, it waits approximately 136 years).
[3.83+] The program "pxelinux-options" can be used to hard-code DHCP options into the "pxelinux.0" image file. This is sometimes useful when the DHCP server is under different administrative control.
6 => 'domain-name-servers',
211 => 'reboottime'
HTTP and FTP
15 => 'domain-name',
54 => 'next-server',
209 => 'config-file',
210 => 'path-prefix',
Older versions of PXELINUX supported HTTP by using a hybrid bootloader that also contained gPXE/iPXE, with such images named either gpxelinux.0 oripxelinux.0.
Since version 5.10, a special PXELINUX binary, lpxelinux.0, natively supports HTTP and FTP transfers, greatly increasing load speed and allowing for standard HTTP scripts to present PXELINUX's configuration file. To use HTTP or FTP, use standard URL syntax as filename; use DHCP options to transmit a suitable URL prefix to the client, or use the "pxelinux-options" tool provided in the "utils" directory to program it directly into the lpxelinux.0 file.
While using HTTP/FTP (syntax), trying to use pxelinux.0 (i.e. without the letter "l" prefix) without iPXE/gPXE running underneath, will result in a"file not found" warning without any explanation as to the cause!
atftp is a client/server implementation of the TFTP protocol that implements RFCs 1350, 2090, 2347, 2348, and 2349. The server is multi-threaded and the client presents a friendly interface using libreadline.