Just in case anyone finds this later, ended up using dnsmasq to make my configuration work using @george1421 's tutorial here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server
Mine was a bit more complicated because I’m running an older version on ubuntu, but @george1421 's tutorial is spot once I got all the other weird things I had to do done lol.
I am OK at wireshark, I’ll give it a shot! Thanks
I can do a capture, but I’m guessing it might have to do with vlans, and each having its own DHCP? I can add the option 66 to the others and see if it helps maybe?
I have option 66 and 67 set, and previously remember using rom-o-matic site to make a few changes that fixed this. Now that the site is down, how do I go about fixing this issue?
Most of my machines are still using legacy boot, but I want to get ready for when that changes soon.
Does it matter after I upgraded that I didn’t get to press Enter after the database update (I think that’s what it said)? Should I rerun the installer one more time?
Thanks,
Good news, I have my 1.2.0 Fog server up again. After building my own ipxe kernel most of my machines can pxe boot properly. I used the bios and uefi @Sebastian-Roth made in that post and both seem to work. Its not asking me for the tftp IP any more and just registered/imaged/deplayed a few machines 
Just wanted to update everyone on where I got today. I was unable to get the trunk version of fog install per these directions: https://wiki.fogproject.org/wiki/index.php?title=Installation#Update_to_latest
So remembering that the content filter was blocking stuff and fixing that let me register clients, upload and deploy images, etc (The only issue that remains is the being prompted for the TFTP server IP), I decided to fire up my attempt at rebuilding our old 0.32 Fog server, and it is doing everything I need it to. I am able to image, upload and deploy, and I never get prompted to put in the TFTP server IP. For that install my option 66 is the server IP as expected, and I am using pxelinux.0 as my boot file for option 66.
I’m hoping that might make since to yall and maybe make something click as to what my problem was with new install (which was 1.2.0->upgraded to a version of trunk that I downloaded on 4/15/2016).
If that makes you think of anything, or you have other questions let me know. Since my immediate need seem to be met for now I was planning on installing 1.2.0 again and fooling with it and see if I can figure out whats going on once I have caught up on other projects.
@Sebastian-Roth OK, thats what i figured but wanted to make sure. I am actaully following george1421 suggestions and setting up a fresh fog server with the trunk version. I will see what those defaults do, and then try out the custom kernel too if I need to.
Tom - Yes, I used this code in rom-o-matic:
#!ipxe
dhcp
set next-server 172.18.164.6
chain tftp://${next-server}/default.ipxe
Does the file name matter? I have been make new name (ie: tom-undionly.kpxe) and not overwriting what was there any more.
@george1421 I have upgraded from 1.2.0 to trunk revision 7188, but can do as you suggested and go straight to trunk on a new VM. I did use a m0n0wall router and made a test network on a unmanaged switch and 1.2.0 worked fine. I just don’t know enough to set up a new DHCP server that will work with my switches and vlan/subnets, etc. on my own. DHCP is handled by a Adtran Netvanta 3140.
@Sebastian-Roth When I used the wiki article you mention, and Tom’s ipxe kernel I get something like “TFTP Error: File not found.” Just in case it matters, the filename the that rom-o-matic gives the file is “ipxe.kpxe”. Also I notice you say which options are yes and no, but some are ticked by default, if it isn’t listed either way in the wiki should I un-tick it?
Tom, when I use that iPXE kernel you suggested i get something similar to the following (transcribed from a video i had to freeze frame to catch lol) :
tftp://172.18.164.6/default.ipxe... ok
params: command not found
Could not boot: Exec format error (http://ipxe.org/2e022001)
Not sure if it matter, but my cell phone videos is hard to read the 0’s or 8’s in that url.
How can I download/overight the files in /tftpboot/ to be the defaults? I should just given them new names but now I can’t remember what I renamed them to 100%.
@Sebastian-Roth I added the option 60, but it didn’t seem to help, but it did give this"
PXE-E51: No DHCP or proxyDHCP offers were received.
Here is a packet capture from the router that the support team was able to set up. Maybe it will shine some light.
0_1461165877412_000001_FOG_1461164083.pcap
undionly.kpxe.new is actaully the original that came with Fog that I renamed.
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://172.18.164.6/fog/service/ipxe/boot.php##params
It still asks me for the IP of the Fog server. This stuff is mostly beyond me but maybe that will help yall out lol.
I built my own iPXE kernel with this:
#!ipxe
dhcp
set next-server 172.18.164.6
set filename undionly.kpxe
chain tftp://${next-server}/${filename}
Then saved the file to my fog server and updated option 67 to the file name. Also changed owner and group. Boot client and at first it didn’t ask for the IP, but it loops and never loads the Fog menu. I think I can see why its doing it but don’t what change.
Fog worked great before so I’m definitely gonna get it working again one way or another. Since our school is fairly small I actually have time over the summer to image computer individual if I need too. At the moment though, I have all the computers on the campus with this Fog server network booting by default. Some of the teachers can handle pressing escape to skip it, so I have to go do it for them. But its a minor inconvenience compared to the power of Fog! I am going to call my switching support and see if they can help me see if the options are being passed. If not I can temporarily move fog to the same sub net and do the tcpdump on it again. If I have to do the capture I will post file.
@george1421 Thanks for the info. I will probably give that a try later, and see how it goes.
I have the option to make the DHCP options be given in either ASCII or as an IP address or hex for that matter. Does is make a difference what I choose?
@george1421 The switches and routers are showing they are in RSTP as far as I can tell. I was reading up on “edge-port mode” for this equipment and it said that “will transition directly in to the forwarding state.” I haven’t put the unmanaged switch between the client and the manage switch again but will see if that helps. I will also add fog to the TFTP field and see if it helps (i think I have before but doesn’t hurt).
I will probably also reach out to my switching support and see if they can help me with option 66 if adding it to the TFTP field doesn’t help.
EDIT: Adding the Fog ip the empty TFTP field didn’t help, also the unmanaged switch between client and core has the same result, still asking for TFTP ip. Is there a way to hard code this somewhere is Fog?
Just an update, I am able to upload and deploy images (once chose the right options for the image lol).
Really the only things that I need to fix now seem to be the TFTP server needing to be input during the boot. I was able to find out the settings that are needed for my Adtran router and switches to TFTP correctly. On the router I had to enable BPDU filter in the Spanning Tree options, then enable edge port mode on the switch ports that have clients. Also make sure your content filter isn’t blocking the Fog server (facepalm). Maybe this can help any one with a similar set up to ours.