@Beyondlimitation the version of dnsmasq you’re running is old. old versions only allowed .0 to be on the tail end of a file name

https://serverfault.com/questions/882554/when-configuring-dnsmasq-for-pxe-booting-why-do-i-need-to-change-undionly-kpxe/882697#882697

@AdrianW are you having this problem on one system, or multiple?

@AdrianW as the user or password been changed since it was last working?

@george1421 said in Where are the general iPXE settings?:

and that should pull the file from the tftpboot directory. But then you will need to have a mac address file for each system. But then what happens if you don’t have a mac address file the boot fails.

in this case, you could just end the chain command with || and it would try the next available command, which can be booting to the fog server

@Gamienator if you’d like examples on how to make iPXE menus (a good starting point) just search the forum for “advanced menu”

@Gamienator ipxe.org has references to all of the commands and functions available, and you can find examples of ipxe menus on the forums.

@Hubi i’m pretty sure there’s references on how to do it on the forums, but here’s how i’ve done it in the advanced menu. it will take just a little modification to put this into the ipxe menu entries instead, but it should give you a pretty good idea of where to start

:Win7SP1x64
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=Win7SP1x64 ftp=${fog-ip} imgType=n imgPartitionType=all osid=5 storage=${fog-ip}:/images/ capone=1
imgfetch init.xz
boot ||
goto MENU

@Hubi ok, that’s a little different. i haven’t touched it in a long time, but we have a plugin called “capone” that does exactly that. i’m not sure if it’s been updated or supported. i just tried to activate it on my dev server and it didn’t work, but that might just be my dev server being a little borken (i’ll leave that typo, it seems fitting).

if the plugin doesn’t work, it can still be done with adding a custom ipxe menu item and setting it as the default for unregistered hosts.

@Hubi that sounds like fog’s normal mode of operation though

you schedule an imaging task telling what hosts to be re-imaged with what image, and on the next boot they do it

what am i missing here?

@Hubi could you provide more details on exactly what you’re trying to do and what you’re trying to achieve? there are multiple ways of doing things that match what you describe, and some of them can have very bad consequences if done without understanding the goal and environment. i wouldn’t want to give you instructions on how to reimage every computer when they boot without an understanding that it’s what you actually want…