General guidance FOG with non mod dhcp.

[JoeCT]

Also changed this line to reflect the ip address of the server

dhcp-boot=undionly.kpxe,x.x.x.x

Sorry about the giant font.

[Tom Elliott]

@JoeCT big font is because of markdown. Wrap the config with three backticks, then new line, the paste contents, new line, three backticks. The back tick usually is shift tilda (~)

[Wayne Workman]

@JoeCT You still need to replace the line “dhcp-boot=undionly.kpxe,x.x.x.x” like I mentioned earlier. Also, it appears that your config is missing the bottom line but I’m assuming that was a copy/paste error.

If you created a symlink named undionly.0 then you need to specify undionly.0 in your ltsp.conf file. Other than that, You’re sym-link looks good.

In other words, the sym-link and the ltsp.conf file must agree with each other lol.

[Tom Elliott]

I think we need to clarify a few things.

DNSMASQ in PROXY DHCP is really strange from my findings. Some of this is a bit old, but still operation.

One of the first things to note.

The bootfile and the pxe items are two SEPARATE THINGS.

Particularly:

dhcp-boot=undionly.kpxe,,x.x.x.x

AND

pxe-service=X86PC, "Boot from network", undionly

With this setup, you will need to create TWO links/copies of the .0 files.

One to undionly.0 from whatever file you want, the other for the first name (undionly.kpxe). (as undionly.kpxe.0)

This is frustrating and confusing I know. Why do it this way I haven’t a clue.

I’d recommend commonize the file names. If your boot file is looking for undionly.kpxe, change the pxe-service line to undionly.kpxe. If you want to use just undionly, then change both lines to show as the same file and create the undionly.0 file to whatever real file you want it to point at.

Hopefully it makes sense.

[Wayne Workman]

@Tom-Elliott It’s really a shame how confusing it is…

I am going to try to write a script that will do all of this stuff for me, and then I’ll share. Give me some time.

[JoeCT]

I think this is what is going on. I am going to try it again tonight. I think I am very close. PXE is very cool. People are booting operating systems, and linux install images with it. Very cool. I did not know it was so powerful.

Thanks for your help guys. I am learning so much from this.

https://forums.fogproject.org/topic/4915/unidonly-0-question

[JoeCT]

Made some progress today. In my research on creating custom pxe boot file for Linux images I found another post talking about customizing ipxe boot files. Interestingly he mentioned adding two lines in the dnsmasq.conf file. In Centos 6.5 this file is in the /etc folder. When I examined the file the two lines where there, but remarked out.

# Include a another lot of configuration options.
conf-file=/etc/dnsmasq.d/ltsp.conf
conf-dir=/etc/dnsmasq.d

After I un-remarked and added the lines above restarted the service and my test system promptly displayed my ipx option option screen 30 second countdown: A network boot, B hard drive boot.

I selected network boot and I was shocked to see the standard fog screen come up. This may have fixed it?

Unfortunately when I tried to register the computer the process jammed with an error

/bzImage32… 21%

I am very close now though and with some more work I think this will work in Centos 6.5 not using fog as a dhcp server but as a proxy dhcp server with the fog pxe boot options.

I am happy. Hope this helps someone else this was painful to figure out. I now understand the .0 automatically being added. I still don’t understand the difference between the undionly.pxe file and the unkionly.kpxe file, but I am taking this as a win!!!

Thanks for your help guys.

[Tom Elliott]

One of the things I always see this issue with is particularly buggy bios. Can you make your symlink point at the undionly.kkpxe rather than the undionly.kpxe?

[Wayne Workman]

@JoeCT Amazing work, that will be going into the new article I’m working on for dnsmasq.

[JoeCT]

I had changed the virtual network on my xp virtual computer which caused the freeze up error. When I change it back to the intel virtual nic the virtual xp connected to fog and I created and restored an image with no issues.

Thank you everyone. Hopefully this will help someone else in future. My distribution was Centos 6.5 and FOG 1.20.