@Wayne-Workman There were other issues like missing kernel command and incorrect variable name as well. Though in current FOG versions you cannot put stuff in /var/www anywhere you like because of our redirect configuration. When you turn on redirect engine debug logging you can see why. I remember having had a first unsuccessful go with trying to come up with a different redirect/rewrite config that works for the API but still allows you to have files pretty much anywhere in /var/www…

What x23piracy posted is also valid but doing it a different way. It boots the ISO without mounting/extracting it first. This does work for some ISOs but causes trouble with others. So this might work but I haven’t tried it myself:

But you need to have the DBAN ISO file in the right place for this as well, /var/www/iso/dban_2.3.0.iso (where /var/www/html/iso/dban_2.3.0.iso does not work in recent FOG versions because of the API redirecting but maybe you’ve switched that off anyway)…

And sorry about the confusion from what is written about DBAN in the wiki!! We need to correct this soon!

@Wayne-Workman Seeing the output /dban/dban.bzi............. I have the impression that it actually starts to load the file properly. AFAIK iPXE is able to “reuse” the IP address from the last HTTP request (loading the menu boot.php). So this should be fine. Though I still think you are right. It ought to be http://${fog-ip}/... or ${boot-url} (hyphen not underscore).

@Arrowtron I am wondering about the connection reset. Are you able to take a packet capture of this? Run tcpdump -w dban.pcap port 80 on your FOG server and boot into the dban thing. Then stop the capture (Ctrl+C), upload to dropbox/googledrive and post a link here.

I think that the ${boot_url} looks blank? Looking at the photo you posted, it just shows /dban/dban.bzi when it should show something more like http://awh-wc-fog/dban/dban.bzi@Sebastian-Roth what do you think? I’m just guessing here.

@Arrowtron Where exactly on the FOG server did you extract the DBAN iso/put the dban.bzi file? There has been some change in HTTP redirecting configuration (for the FOG API) that might get in the way here.