[dhcp] root=D:\PXE filename=bootfiles\undionly.kpxe
Problem setting Root and filename, altfilename
#1
Posted 29 January 2018 - 03:04 PM
#2
Posted 29 January 2018 - 06:20 PM
Hello,I have a problem setting root and filename directives in config.ini.These two directives seem to be strongly correlated, I would like that filename path could be relative to root. For example:[dhcp] root=D:\PXE filename=bootfiles\undionly.kpxeIt it works, by this, I can put all my boot files in D:\PXE\bootfiles. But currently withTiny PXE server (pxeserv.exe) v1.0.0.21, the previous directives change the PXE server rootto "d:\PXE\bootfiles" (seen in server output) instead of keeping "d:\PXE" as I want. Tiny PXE server is located at d:\PXE\pxeserv.exe.Is there a solution for that?
You have probably already considered it but i'll have to ask
Have you considered the below?
Stuff your exe in d:\pxe and your boot files (boot strap, iso, wim, etc) in .\bootfiles ?
[dhcp] root=D:\PXE\bootfiles filename=undionly.kpxe
#3
Posted 29 January 2018 - 07:04 PM
#4
Posted 29 January 2018 - 09:17 PM
@erwan.lFor me the root directory once set in config.ini by root= directive should not be changed later at run-time. Otherwise this is confusing.Filename, Altfilename directives path etc... could then be relative to this root directory.The directory where pxeserv.exe is started does not seem to have importance, but it seems that it looks for config.ini in the same directory.To access wim/iso etc... files by httpd or nfs server, I can use "/../" to traverse the directory tree, there is no problem.
Fair point : at first look it is an un-expected side effect (i dont recall this being a request in the past).
I will have a look by the end of this week.
It has been ages that I did not release a new version : I take it this is a sign of stability
#5
Posted 30 January 2018 - 08:11 AM
#6
Posted 02 February 2018 - 05:40 PM
@ktp
1.About INADDR_ANY : try '0.0.0.0' in the config.ini but then you will have to take care of all fields.
2.In latest version, you can use CTRL+R to refresh interfaces (without restarting the software).
3.IPV6 ... tough one
- ktp likes this
#7
Posted 02 February 2018 - 09:03 PM
@ktp : i can probably enforce that "root=root" but are you sure that pxe clients will be happy file boot filename = "bootfiles\undionly.kpxe" ?
is that long string supported? can you use '\' char in a filename?
#8
Posted 03 February 2018 - 07:06 AM
#9
Posted 03 February 2018 - 11:41 AM
- ktp likes this
#10
Posted 03 February 2018 - 11:43 AM
I could do it as well.
#11
Posted 03 February 2018 - 02:28 PM
About point 1 i suspect aoemi pxe is using the best interface to provide valid ip détails / dhcp options.
I could do it as well.
Yes, please do it, it would greatly help.
What I understand is that when a DHCP DISCOVER is received on one interface, TPS will use all the default/best options (IP pool start/size, next-server, options 1,3,6,28 as displayed in the GUI) to send back to the PXE client and handling subsequent TFTP/HTTP requestts. And of course Proxy DHCP or not should be taken into account.
Question: in case option54=0.0.0.0, I assume the checkbox "Bind" is no longer necessary or ineffective. Is it true?
#12
Posted 03 February 2018 - 02:39 PM
#13
Posted 03 February 2018 - 02:44 PM
About point 2 you need to download latest zip.
Got it and tested OK. On Ctrl-R pressed, new message displayed in log file, announcing the total number of interdaces (operational or not), and what best interface is.
The option 54 combo-box (list of interfaces) is updated accordingly to add new operational interfaces, or to suppress down interfaces. Note: so the number of elements in the combo-box could be less than the total number of interfaces due to some inoperational/disconnected interface.
pxeserv.exe size 922,112 bytes, date 2018-02-02 (yyyy-mm-dd).
MD5 fba2a527a1b836631f59d122f4b9d5e4 *pxesrv.exe
#14
Posted 03 February 2018 - 02:48 PM
The option 54 combo-box (list of interfaces) is updated accordingly to add new operational interfaces, or to suppress down interfaces. Note: so the number of elements in the combo-box could be less than the total number of interfaces due to some inoperational/disconnected interface.
Actually and you spot it right : it will always report +1 interface as I am actually removing the '0.0.0.0' on purpose today
This mis design thingie is there since day one : option 54 <> interface card.
Next version will have a new field for interfaces, above the option 54 field, and will list all interfaces including '0.0.0.0'.
Yes, non connected interfaces (or rather those without an IP), will be not listed.
#15
Posted 04 February 2018 - 03:58 PM
pxesrv.exe 1.0.0.21 04/02/2018 14:08 CC9234D6500082C7C509E64FB6BE0F2F
[dhcp] ;root= filename=bootfiles\unkdionly.kpxe altfilename=menu.ipxe
[arch] ; http://reboot.pro/topic/21614-ipxe-wimboot-and-multi-platform-pcbiosefii386x86-64/ ; will overrule filename or opt67 if client arch matches one of the below ; DHCP option 93 Client architecture ; 0 Standard PC BIOS ; 6 32-bit x86 EFI ; 7 64-bit x86 EFI ; 9 64-bit x86 EFI (obsolete) ; 10 32-bit ARM EFI ; 11 64-bit ARM EFI 00000=bootfiles\undionly.kpxe 00006=bootfiles\ipxe32.efi 00007=bootfiles\ipxe64.efi [dhcp] ;root= filename=unkdionly.kpxe altfilename=menu.ipxe
Directory \PXE: TPS files: pxesrv.exe (main executalbe) config.INI (configuration file) menu.ipxe (altfilename: menu for iPXE) Optional: licensing.txt pxesrv.txt pxesrv-faq.xhtml version.txt Directory \PXE\bootfiles\: bootfiles: *.efi *.pxe *.k*pxe
#16
Posted 04 February 2018 - 05:14 PM
Good news is that there is a workaround
Actually this should be the default behavior.
I reckon there is something wrong around the (main) boot filename and the root variable.
About point 1 : by design, if no root variable then root = exe directory.
About point 2 : this has indeed to be part of the workaround (you could even put a dummy filename there).
About point 3 : part of the workaround for now, has to take place thru the ini file.
About point 4 : ouch ... you may not like it look under HKLM\software\iptools\pxeserver\txtaltfilename .
I could change HKLM to HKCU thus...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users