Jump to content











Photo

Bug Reports, Requests, HowTo's about Tiny PXE Server

pxe network boot

  • Please log in to reply
779 replies to this topic

#201 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 08:28 AM

please add a Save command button in interface of your soft.

add a item to define or modify [arch] section of config.ini,too.

 

in your last version,I pre-define "root" ,"filename" in config.ini,then run the pxesrv.exe,the EFI client boot fail,but,in  soft interface I define "Filename ",then the EFI client boot success.why?

 

the [arch] item boot EFI fail as before.


Edited by hhh333, 19 September 2014 - 09:05 AM.


#202 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 19 September 2014 - 08:59 AM

please add a Save command button in interface of your soft.

add a item to define or modify [arch] section of config.ini,too.

 

in your last version,I pre-define "root" ,"filename" in config.ini,then run the pxesrv.exe,the EFI client boot fail,but,in  soft interface I define "Filename ",then the EFI client boot success.why?

 

Adding a save button is a good idea : will probably do in next version.

 

Adding a button to modify the config.ini added little or no added value, IMHO.

 

About the EFI boot not working when pre defining the config.ini, can you add verbose=1 under [dhcp] section and send me the entire log (as displayed in the main window).

 

Thanks for your feedback,

Erwan



#203 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 12:01 PM

the config.ini:

[arch]
00006=bootia32.efi
00007=bootx64.efi

[dhcp]
root=c:
Filename=bootx64.efi
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 

[frmDHCPServer]
top=272
left=989

then boot EFI fail,this is the log:

19:38:18 ROOT=c:\
19:38:18 DHCPd:67 started...
19:38:18 TFPTd started...
19:38:19 HTTPd started...
19:38:59 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:FD5189EB
19:38:59 DHCPd:OFFER sent, IP:192.168.1.221, XID:FD5189EB
19:39:02 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:FD5189EB
19:39:03 DHCPd:Arch=00007
19:39:03 DHCPd:ACK sent, IP:192.168.1.221, XID:FD5189EB
19:39:03 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:39:04 TFTPd:received TFTP_ERROR
19:39:04 TFTPd:Exception:Operation aborted
19:39:04 TFTPd:TransferComplete=True (192.168.1.221:1318)

click Filename button,then assign to c:\bootx64.efi,then EFI client boot success,the log as follow:

19:40:06 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:146CC1C7
19:40:06 DHCPd:OFFER sent, IP:192.168.1.221, XID:146CC1C7
19:40:10 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:146CC1C7
19:40:10 DHCPd:Arch=00007
19:40:10 DHCPd:ACK sent, IP:192.168.1.221, XID:146CC1C7
19:40:10 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:40:13 TFTPd:TransferComplete=True (192.168.1.221:1082)
19:40:13 TFTPd:DoReadFile:\BCD B:0 T:20480
19:40:13 TFTPd:received TFTP_ERROR
19:40:13 TFTPd:Exception:Operation aborted
19:40:13 TFTPd:TransferComplete=False (192.168.1.221:10111)
19:40:13 TFTPd:DoReadFile:\Boot\BXE B:0 T:20480
19:40:13 TFTPd:received TFTP_ERROR
19:40:13 TFTPd:Exception:Operation aborted
19:40:13 TFTPd:TransferComplete=False (192.168.1.221:10112)
19:40:13 TFTPd:DoReadFile:\Boot\BXE B:1456 T:20480
19:40:13 TFTPd:TransferComplete=True (192.168.1.221:10113)
19:40:13 TFTPd:OpenError:Cannot open file "c:\en-US\bootx64.efi.MUI". 系统找不到指定的路径。
19:40:13 TFTPd:OpenError:Cannot open file "c:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。
19:40:13 TFTPd:OpenError:Cannot open file "c:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。

(in my bootx64.efi already modify BCD to BXE)

 



#204 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 19 September 2014 - 06:57 PM

 

the config.ini:

[arch]
00006=bootia32.efi
00007=bootx64.efi

[dhcp]
root=c:
Filename=bootx64.efi
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 

[frmDHCPServer]
top=272
left=989

then boot EFI fail,this is the log:

19:38:18 ROOT=c:\
19:38:18 DHCPd:67 started...
19:38:18 TFPTd started...
19:38:19 HTTPd started...
19:38:59 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:FD5189EB
19:38:59 DHCPd:OFFER sent, IP:192.168.1.221, XID:FD5189EB
19:39:02 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:FD5189EB
19:39:03 DHCPd:Arch=00007
19:39:03 DHCPd:ACK sent, IP:192.168.1.221, XID:FD5189EB
19:39:03 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:39:04 TFTPd:received TFTP_ERROR
19:39:04 TFTPd:Exception:Operation aborted
19:39:04 TFTPd:TransferComplete=True (192.168.1.221:1318)

click Filename button,then assign to c:\bootx64.efi,then EFI client boot success,the log as follow:

19:40:06 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:146CC1C7
19:40:06 DHCPd:OFFER sent, IP:192.168.1.221, XID:146CC1C7
19:40:10 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:146CC1C7
19:40:10 DHCPd:Arch=00007
19:40:10 DHCPd:ACK sent, IP:192.168.1.221, XID:146CC1C7
19:40:10 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:40:13 TFTPd:TransferComplete=True (192.168.1.221:1082)
19:40:13 TFTPd:DoReadFile:\BCD B:0 T:20480
19:40:13 TFTPd:received TFTP_ERROR
19:40:13 TFTPd:Exception:Operation aborted
19:40:13 TFTPd:TransferComplete=False (192.168.1.221:10111)
19:40:13 TFTPd:DoReadFile:\Boot\BXE B:0 T:20480
19:40:13 TFTPd:received TFTP_ERROR
19:40:13 TFTPd:Exception:Operation aborted
19:40:13 TFTPd:TransferComplete=False (192.168.1.221:10112)
19:40:13 TFTPd:DoReadFile:\Boot\BXE B:1456 T:20480
19:40:13 TFTPd:TransferComplete=True (192.168.1.221:10113)
19:40:13 TFTPd:OpenError:Cannot open file "c:\en-US\bootx64.efi.MUI". 系统找不到指定的路径。
19:40:13 TFTPd:OpenError:Cannot open file "c:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。
19:40:13 TFTPd:OpenError:Cannot open file "c:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。

(in my bootx64.efi already modify BCD to BXE)

 

 

Ok, i uploaded a new version.

Thanks to your reports, i found a "nice" bug (here since day 1) : Opt13 (boot filename size) was incorrect when loading a filename thru config.ini.

It seems my pxe client over here did not care but this was definitely wrong and could possibly be your issue.

 

Give it a new try.

 

This is too soon to discuss and I dont want to deviate for now but you dont need to patch your bootx64.efi : you could use option 252 instead.

See screenshot here.



#205 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 09:20 PM

config.ini

[arch]
00006=bootia32.efi
00007=bootx64.efi

[dhcp]
root=c:\
Filename=pxelinux.0
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 

[frmDHCPServer]
top=167
left=1188

the log:the arch does not work sucess.

5:14:23 ROOT=c:\
5:14:23 DHCPd:67 started...
5:14:23 TFPTd started...
5:14:23 HTTPd started...
5:14:38 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:8C28A167
5:14:39 DHCPd:OFFER sent, IP:192.168.1.221, XID:8C28A167
5:14:42 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:8C28A167
5:14:42 DHCPd:Arch=00007
5:14:42 DHCPd:ACK sent, IP:192.168.1.221, XID:8C28A167
5:14:42 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
5:14:44 TFTPd:TransferComplete=True (192.168.1.221:1311)

in interface of soft to assign Filename to bootx64.efi,then EFI client boot success:

5:17:32 ROOT=C:\
5:17:32 DHCPd:67 started...
5:17:32 TFPTd started...
5:17:32 HTTPd started...
5:17:42 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:8C28A168
5:17:43 DHCPd:OFFER sent, IP:192.168.1.221, XID:8C28A168
5:17:46 DHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, XID:8C28A168
5:17:46 DHCPd:Arch=00007
5:17:46 DHCPd:ACK sent, IP:192.168.1.221, XID:8C28A168
5:17:46 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
5:17:48 TFTPd:TransferComplete=True (192.168.1.221:1312)
5:17:48 TFTPd:DoReadFile:\BCD B:0 T:20480
5:17:48 TFTPd:received TFTP_ERROR
5:17:48 TFTPd:Exception:Operation aborted
5:17:48 TFTPd:TransferComplete=False (192.168.1.221:8766)
5:17:48 TFTPd:DoReadFile:\Boot\BXE B:0 T:20480
5:17:48 TFTPd:received TFTP_ERROR
5:17:48 TFTPd:Exception:Operation aborted
5:17:48 TFTPd:TransferComplete=False (192.168.1.221:8767)
5:17:48 TFTPd:DoReadFile:\Boot\BXE B:1456 T:20480
5:17:48 TFTPd:TransferComplete=True (192.168.1.221:8768)
5:17:48 TFTPd:OpenError:Cannot open file "C:\en-US\bootx64.efi.MUI". 系统找不到指定的路径。
5:17:48 TFTPd:OpenError:Cannot open file "C:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。
5:17:48 TFTPd:OpenError:Cannot open file "C:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf". 系统找不到指定的路径。



#206 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 19 September 2014 - 09:26 PM

sorry, I did not catch it : do you mean "does work -> success" or "does not work -> failure" ?

 

looking at your log file, it seems to work in all cases now.

 

 

the log:the arch does not work sucess.



#207 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 19 September 2014 - 09:28 PM

in your config.ini, I would add under [dhcp] : opt252=@arch\bcd

 

then in folder 00007, put BCD for x64 EFI and in folder 00006, put  BCD for x32 EFI.



#208 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 09:33 PM

suggest:

1.let the Filename and [arch] section to use relation path.(as HaneWin)

2.let [arch] section work success.

3.let every config in config.ini can modify in soft interface,and let user to decide to save or not.



#209 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 09:54 PM

now,the key point is :begin soft ,the EFI client boot fail,but if I assign Filename to C:\bootx64.efi in soft interface,the EFI client boot success.

so,I guess the [arch] setion can not work success. 



#210 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 10:07 PM

now,i use the original bootx64.efi,

the config.ini,EFI client success

[arch]
00006=bootia32.efi
00007=bootx64.efi

[dhcp]
root=c:\
Filename=bootx64.efi
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 
opt252=efi\microsoft\boot\@arch\bcd

[frmDHCPServer]
top=167
left=1188

but if let Filename=pxelinux.0 in config.ini,EFI boot fail



#211 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 19 September 2014 - 10:17 PM

I test this config.ini also,delete [arch] setion,then efi boot success:
[dhcp]
root=c:\
Filename=bootx64.efi
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 
opt252=efi\microsoft\boot\@arch\bcd

[frmDHCPServer]
top=167
left=1188

the opt252 work very good

Edited by hhh333, 19 September 2014 - 10:23 PM.


#212 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 19 September 2014 - 10:52 PM

now,i use the original bootx64.efi,
the config.ini,EFI client success

[arch]
00006=bootia32.efi
00007=bootx64.efi

[dhcp]
root=c:\
Filename=bootx64.efi
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1 
opt252=efi\microsoft\boot\@arch\bcd

[frmDHCPServer]
top=167
left=1188

but if let Filename=pxelinux.0 in config.ini,EFI boot fail

Ok we are getting there.
I will test this scenario tomorrow.

Thanks a lot for your patience and feedback!

#213 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 20 September 2014 - 12:16 PM

I tested the below config.ini.
Indeed, found the following bug : when switching to arch=00007 (i.e bootx64.efi), Tiny PXE Server would incorrectly set opt13=size_of_filename (i.e size of pxelinux.0).
This is now fixed in latest upload.

Surprisingly (again), my pxe clients over here would not care about this but this is definitely wrong and would affect pxe client out there.

[arch]
00006=bootia32.efi
00007=bootx64.efi 

[dhcp]
root=c:\
Filename=pxelinux.0
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1
opt252=efi\microsoft\boot\@arch\bcd


#214 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 20 September 2014 - 01:14 PM

suggest:

1.let the Filename and [arch] section to use relation path.(as HaneWin)

2.let [arch] section work success.

3.let every config in config.ini can modify in soft interface,and let user to decide to save or not.

 

1.

You can use relative path in root like root=my_folder. This folder then needs to be existing in the current folder where TPS is executed.

You can also use relative path in [arch] section like 00007=efi\bootx64.efi. TPS will then look for it in the current defined root.

 

2.

[arch] should by now (hopefully) works

 

3.

will eventually add a save button.



#215 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 20 September 2014 - 02:04 PM

I tested,very good!
1.relative path,OK 00007=efi\boot\iPXE64.efi,OK!
2.[arch] section,OK,this is my config.ini

[arch]
00006=efi\boot\bootia32.efi
00007=efi\boot\iPXE64.efi
[dhcp]
root=c:\
Filename=pxelinux.0
tftpd=1
httpd=1
binl=0
start=1
proxydhcp=0
bind=1
smb=0
verbose=1

3.Waitig your SaveButton and method to access every parameter in config.ini by through soft interface......thanks


Edited by hhh333, 20 September 2014 - 02:52 PM.


#216 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 21 September 2014 - 07:55 AM

If i modify config.ini,i must reload this soft,then the modified section take effect.

i can't to use 'offline' then "online" button to take effect.



#217 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 21 September 2014 - 10:07 AM

If i modify config.ini,i must reload this soft,then the modified section take effect.

i can't to use 'offline' then "online" button to take effect.

 

download latest version : 

added : can re load settings from config.ini
added : can save settings to config.ini
added : smb checkbox
 

about reload settings, it is advised to click the "offline" button first.

about save settings, a few settings are excluded for now : log, verbose, cmd, start, tftp (default=1), and the [arch] section.

 

x5cm2V7.png



#218 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 26 September 2014 - 07:31 AM

if my server IP is 192.168.1.254,then run this soft ,the "IP Pool start" is seted 192.168.1.255 automatically ,it's wrong obviously



#219 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 27 September 2014 - 11:34 AM

if my server IP is 192.168.1.254,then run this soft ,the "IP Pool start" is seted 192.168.1.255 automatically ,it's wrong obviously

 

Indeed, to set the poolstart, I use the host ip +1.

I'll handle this case.

Note that this field is automatically set (and will be fine in most cases), but the user can/should review it before starting.



#220 pbmarler

pbmarler
  • Members
  • 1 posts
  • Location:Indianapolis
  • Interests:VMware, Netboot, PXE, iPXE, Tiny PXE Server, Live Boot Mastering
  •  
    United States

Posted 29 September 2014 - 11:18 PM

To erwan.l,
 
I really like Tiny PXE Server! Thanks so much for making it! I can boot QuickPE and start Windows installations via net use paths thanks to http://labalec.fr/erwan/?p=773. Using your :pmagic entry as an example from your menu.ipxe, I have no trouble deploying ESXi 5.5 via ISO images. I was also able to get Redo to work over NFS from menu.ipxe after adjusting the NFS path for my configuration. I've also had luck network booting and installing Debian 7. Thanks again for such an awesome program! 
 
To anyone with interest in helping,
 
Has anyone had any success with network booting the latest version of the FreeNAS installer with Tiny PXE Server? (http://www.freenas.o...as-release.html) If so, would you be willing to share the ipxe commands you used? Is there another forum, topic or resource for sharing such recipes? Thanks for reading my post!


#221 tqangxl

tqangxl
  • Members
  • 2 posts
  •  
    China

Posted 14 November 2014 - 11:03 PM

Good work, have to replace all the trend of similar products, gas!
If we can improve the following function is very good
1.psl add an embedded script retry automatically loads default.ipxe file . like this function to avoid DHCP get ip address cycle.
2.add save config and relode config function
3.add profile manager ,if chose this profile will display all this profile setting!
4.gpxe or ipxe can be browser file ,filename and gpxe or ipxe need file path
5.ipxe 1.0.0.+open network firm to config net0 always filed
6.languages . pls use ini file translated into different languages
7.If all the configuration file settings, can in the graphical interface operation completion is very beautiful.
8.add dhcp option 82 61 116 120 42
9.add pxe boot need password(option)
10.add allow multicast(maybe)
11.documents need more and more !!!!
12.httpd you can use http://www.rejetto.com/hfs/?f=dl
download sources: http://downloads.sou...hfs2.3d.src.zip
13. about SMB, maybe have windows authentic,eg.windows domain

on vmware system :win7 32bit pro use this tool for Microsoft Deployment Toolkit 2013 PXE Boot capture client and deploy windows 7 & 8 & 8.1
issue:
1.The machine boot sequence
00000=ipxe/pcibios/ipxe.pxe —->00009=default.ipxe After the failure of this will go to your menu.So there may be problems of place, please check and repair pls check log
2. if file ‘D:\Lib\Soft\TFTP_Server\Tiny-PXE-Server\files\ipxe\default.ipxe-‘ change to ‘D:\Lib\Soft\TFTP_Server\Tiny-PXE-Server\files\ipxe\default.ipxe’
The contents of the file is changed into will work:
————————————————–
#!ipxe

echo Hello, world!

#chain /ipxe/wimboot.txt ||
#chain http://boot.rackspace.com/menu.ipxe
#shell
set boot-url http://${dhcp-server}
kernel ${boot-url}/wimboot.i386
initrd ${boot-url}/BOOTMGR BOOTMGR
initrd ${boot-url}/BOOT/BCD BCD
initrd ${boot-url}/BOOT/BOOT.SDI BOOT.SDI
initrd ${boot-url}/SOURCES/BOOT.WIM BOOT.WIM
boot

exit
—————————————————–

3.your config get operation not supported or nic no found
The problem of playback way: modify config.ini eg: ;00009=default.ipxe

log:

4:01:17 ROOT=D:\Lib\Soft\TFTP_Server\Tiny-PXE-Server\files\
4:01:17 DHCPd:67 started…
4:01:17 DHCPd:4011 started…
4:01:17 TFPTd started…
4:01:18 HTTPd started…
4:01:18 SMB failed: 0
4:01:18 DNSd:53 started…
4:01:29 DHCPd:DISCOVER received, MAC:00-50-56-3F-4C-2B, XID:573F4C2B
4:01:29 DHCPd:OFFER sent, IP:0.0.0.0, XID:573F4C2B
4:01:31 DHCPd:REQUEST discarded, MAC:00-50-56-3F-4C-2B, XID:573F4C2B
4:01:31 PDHCPd:REQUEST received, MAC:00-50-56-3F-4C-2B, IP:192.168.52.128, XID:573F4C2B
4:01:31 Proxy boot filename empty?
4:01:31 PDHCPd:DHCP_ACK sent, IP:192.168.52.128:68, xid:573F4C2B
4:01:31 TFTPd:DoReadFile:ipxe/pcibios/ipxe.pxe B:0 T:392457
4:01:31 TFTPd:DoReadFile:ipxe/pcibios/ipxe.pxe B:1456 T:0
4:01:57 DHCPd:DISCOVER received, MAC:00-50-56-3F-4C-2B, XID:26222502
4:01:57 DHCPd:iPXE user-class detected
4:01:57 DHCPd:OFFER sent, IP:0.0.0.0, XID:26222502
4:01:57 DHCPd:REQUEST discarded, MAC:00-50-56-3F-4C-2B, XID:26222502
4:02:03 TFTPd:OpenError:Cannot open file « D:\Lib\Soft\TFTP_Server\Tiny-PXE-Server\files\ipxe\default.ipxe ». 系统找不到指定的文件。(conn’t find this file)
4:02:03 TFTPd:DoReadFile:/menu.ipxe B:1432 T:11675

ref:



#222 tqangxl

tqangxl
  • Members
  • 2 posts
  •  
    China

Posted 14 November 2014 - 11:18 PM

1.pls update syslinux 

 

https://www.kernel.o.../boot/syslinux/

 

2. add retry 

3.pls add  function:

pls check  :

http://www.syslinux....ex.php/PXELINUX

 

and find this part:

DHCP options 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).

 

Hardcoded options

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

Hardcoded options:

6 => 'domain-name-servers',
15 => 'domain-name',
54 => 'next-server',
209 => 'config-file',
210 => 'path-prefix',

211 => 'reboottime' HTTP and FTP

 

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!

 

 

 

 

 

ref:

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.



#223 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2281 posts
  • Location:Nantes - France
  •  
    France

Posted 15 November 2014 - 02:40 PM

1.pls update syslinux 

 

https://www.kernel.o.../boot/syslinux/

 

2. add retry 

3.pls add  function:

pls check  :

http://www.syslinux....ex.php/PXELINUX

 

and find this part:

DHCP options 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).

 

Hardcoded options

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

Hardcoded options:

6 => 'domain-name-servers',
15 => 'domain-name',
54 => 'next-server',
209 => 'config-file',
210 => 'path-prefix',

211 => 'reboottime' HTTP and FTP

 

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!

 

 

 

 

 

ref:

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.

 

it is a long post touching various topics ... :)

 

About "1.pls update syslinux", pxesrv.zip includes an older version on purpose as latest syslinux cannot be chainloaded from ipxe (my main driver).

See here.

Thus, Tiny PXE Server works perfectly fine with latest syslinux 6.x versions. Therefore feel free to include it in your pxesrv.zip.

 

About "2. add retry". please be more specific.

I can only tell for now that I rely on client protocol (dhcp, tftp, etc) to "retry" by themselves.

 

About "3.pls add  function".

Tiny PXE Server has a field "extra option" where you can specify any dhcp option.

I aggree that this is not obvious nor friendly (hopefully Wonko wont see this :) ).

for example : 211.90 would set the pxelinux.reboottime to 90.

Alphacharacters need to be translated to numeric

 

Regards,

Erwan



#224 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14225 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 November 2014 - 04:28 PM

I aggree that this is not obvious nor friendly (hopefully Wonko wont see this  :) ).

 

 

Oww. come on :whistling:, playing ;) with logical impossibilities again?  :w00t:

 

Spoiler

 

:duff:

Wonko



#225 ZEE

ZEE

    Member

  • Members
  • 96 posts
  •  
    Portugal

Posted 27 November 2014 - 08:34 PM

hi ppl...

 

tinypxe was working ok in a old version (10.0.0.11 i think...)

just downloaded the last version (10.0.0.18) and start to have a problem...

everything runs ok until start transmitting the TFTP boot file (grldr in this case)

 

try the very same configurations in my reserve DHCP/TFTP server (TFTP32) and everything runs OK...

 

disabled firewall, checked event logs, etc. etc.  *?!puzzled!?* worked fine before

i send below the messages in the log panel from tinypxe...

cumps ZEE

 

 

20:22:28 ROOT=D:\{live}\
20:22:28 DHCPd:67 started...
20:22:28 TFPTd started...
20:22:35 DHCPd:DISCOVER received, MAC:60-A4-4C-75-80-73, XID:4D758073
20:22:36 DHCPd:OFFER sent, IP:10.0.0.201, XID:4D758073
20:22:37 DHCPd:REQUEST received, MAC:60-A4-4C-75-80-73, XID:4D758073
20:22:38 DHCPd:ACK sent, IP:10.0.0.201, XID:4D758073
20:22:38 TFTPd:DoReadFile:grldr B:1456 T:0
20:22:40 TFTPd:TFTPException:Unexpected operation from 10.0.0.201:2071
20:22:42 TFTPd:TFTPException:Timeout
 







Also tagged with one or more of these keywords: pxe, network boot

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users