Jump to content











Photo

All possible parameters in Tiny PXE Server configuration file

tiny pxe server configuration

  • This topic is locked This topic is locked
No replies to this topic

#1 erwan.l

erwan.l

    Gold Member

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

Posted 22 September 2013 - 04:45 PM

The configuration must be named config.ini and must stand in the same folder as Tiny PXE server.

 

Here below all possible values to be found in config.ini.

 

[arch]

;will overrule filename or opt67 if client arch matches one of the below
00006=bootia32.efi
00007=bootx64.efi

 

[dhcp]
;needed to tell TFTPd where is the root folder
; example root=C:\pxe or root=pxe (software will then look for pxe folder below the folder where it stands)
root=pxe
;boot file - can be empty if you boot directly with ipxe/gpxe rather than intel pxe agent
filename=ipxe-undionly.kpxe
;alternative boot file if request comes from ipxe or gpxe
;you can use @arch or @mac in altfilename
altfilename=menu.ipxe
;my gpxe / ipxe dhcp options
optextra=175.6.1.1.1.8.1.1
;start the following daemons
httpd=1
proxydhcp=0
binl=0
dnsd=0
;will (netbios) share the root folder as PXE
smb=1
;default value for tftpd=1
;tftpd=0
;start auto
start=0
;bind=1 by defaukt
;bind=0
;syslog=127.0.0.1
;dhcp options
;next-server=
;opt1=
;opt3=
;opt6=
;opt15=
;opt17=
;opt28=
;opt43=
;opt51=
;opt54=
;opt66=
;opt67 will overrule filename, \0 will be replaced by null char (needed by some pxe clients)
;opt67=
;you can use @arch or @mac in opt252
;opt252=
;proxybootfilename=
;poolstart=
;poolsize=
;the below will enable support for bootp clients (next to dhcp clients)
;rfc951=1
;online=any batch/executable you want to be launched when pushing start like a nfs server
;offline=any batch/executable you want to be launched when pushing stop
;wsMinimized=0
 
[web]
;default value=80
;port=80





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users