I have a server which is running Pi-Hole with DHCP enabled. I would like to run iVentoy on the same machine.
So I switched DHCP server mode to external (hoping it would disable the DHCP server ran by iVentoy) and clicked start. Which resulted in iVentoy telling me that it could not bind the port:
Code:
2023/06/30 20:34:42.135 [HTTP] API request: <{"method":"start_server","ip":"10.69.42.42","mask":"255.255.255.0","gw":"10.69.42.1","pool_begin":"10.69.42.200","pool_end":"10.69.42.219"}>
2023/06/30 20:34:42.135 [DHCP] DHCP port 67(UDP) is in use now.
What works (internal DHCP):
- PXE asks for DHCP -> gets anwer from main DHCP
- gets IP from main DHCP-Server
- sends iventoy_loader_16000
- asks iVentoy DHCP for new IP
Boot successful
Windows 11 install successful (even with unattend.xml, only partitioning was manual, from boot to login)
BUT after i login to windows i get only the ip from iVentoy-DHCP and therefore i cant access the internet cause of my very complicated DNS setup (gateway and dhcp is 254, nameserver is 1, a pihole-dns)
Conclusion my OpenWRT main DHCP and iVentoy are fighting for the World dominance, not good
Idea use external function from iVentoy but cant get it to boot since i don't know which file i should serve or which options other than 66,67,150 i need to get it to boot.
Next Problem is i have to restart iVentoy after a successful PXE boot, because if in the webgui the device is listed, i get TFTP file not found
FEATURE REQUEST:
- possibility to set a nameserver in DHCP options (option '6')
BUGS FOUND:
- iVentoy does not save gateway...
- iVentoy forgets Auto Install Script settings after Image refresh (nags me hard)
Any Ideas welcome
EDIT: for the interrested, the unattend.xml is attached, have to change to your language values (mine is German), your license key and username+password and maybe Windows 11 version as mine is Pro
Lincense key inside is the official Windows 11 Pro volume key (puplic on Microsoft site)
As you can see ive tried also the native "libevent" shipped with debian by simply removing it from the lin64 folder but the same issue.
Is there a way to completely disable the internal DHCP, i tried using "ipxe.bios.0" while setting external DHCP but no success.
Thanks in advance
Phil2Sat
EDIT: It seems iVentoy needs at least two CPU cores, which is in case of a virtual environment not that good.
BTW: the gateway ip gets not saved and i have to set it all the time.
I am trying to get the minstall programs to load automatically in Sergei Strelec latest ISO, and I have tried calling the vtoymnt.bat from startnet.cmd by editing it in the strelec10x64Eng.wim (for example) and resaving the ISO.
This does not mount Y: as I expected, but my changes do show up in the x:\window\system32\startnet.cmd file. I have tried using both of the following:
start x:\vtoymnt.bat Y
call x:\vbtoymnt.bat Y
Is there a different way I can accomplish this, or am I using the wrong commands/syntax?
As we always keep our machines in Secure Boot, is it possible to enable/allow secure boot with iVentoy, maybe even with the same signature as Ventoy that we have already added to many of our machines in MOK enrollment?
1. Perhaps there is a "new PXE client" configuration (or "boot once" configuration) that can be used just to get the machine to boot into an ISO just one time.
1a. Also allow selection for injections/auto install script, etc.
2. Control which network interface the GUI can be accessed from (so not just 127.0.0.1:26000). Only allow once a username and password have been set.
3. Add image file upload capability to the GUI which will save files to the ISO location
3a. Configure the locations to search for ISO files on the server (not just the ISO location)
4. Perhaps when a machine boots to the iVentoy menu, the iVentoy web interface can allow us to control/select the option currently displaying on the endpoint instead of having to have a mouse/keyboard/monitor on the endpoint (which would help for remote reinstall scenarios). This may be difficult to implement but would be very useful.
5. Would like a command line option to use as a Windows Service (no GUI) so that when the PXE server is rebooted, iVentoy will start running again automatically.
I would very happily consider donation over and above the $49 commercial donation for these features.