PXEBoot, DHCP failure.
-
if you are running fog 1.0+ the bootfile name is now undionly.kpxe
that is why it is important to pay attention to the instructions in the installer -
Yep,
The installer for 1.x.x tells you to use option 67 with undionly.kpxe
-
So changing option 67 to now read undionly.kpxe and then trying to initialise a network boot still returns the same TFTP open timeout, any other possbile suggestions?
Also I have been through the forums and noted people are saying to:
sudo service tftpd-hpa start
sudo service tftpd-hpa stopDoesn’t seem to make any difference for me.
-
Check your permissions on the /tftpboot folder.
They seem to work best set as:
[code]chown -R fog:{webuser e.g. www-data for debian insts, apache for red hat insts)
chmod -R 667 /tftpboot[/code] -
Thanks for your reply! I’ve just changed the permissions as you advised, but still having the same TFTP open error?
[url=“/_imported_xf_attachments/1/1063_Error.png?:”]Error.png[/url]
-
This post is deleted! -
OK in an attempt to try provide you guys with as much info as possible I have tried to pull the file from the Fog Server through Windows… this works?
[url=“/_imported_xf_attachments/1/1065_Error.png?:”]Error.png[/url][url=“/_imported_xf_attachments/1/1066_DHCP.png?:”]DHCP.png[/url]
-
[quote=“rjn239, post: 31261, member: 24764”]OK in an attempt to try provide you guys with as much info as possible I have tried to pull the file from the Fog Server through Windows… this works?[/quote]
At this point I recommend using DNSMASQ to help resolve your boot file.
It’s a simple set up and easy to remove.
-
[quote=“Jaymes Driver, post: 31264, member: 3582”]At this point I recommend using DNSMASQ to help resolve your boot file.
It’s a simple set up and easy to remove.[/quote]
Thanks for the alternative, seems like a good work around. Only problem is after implementing and getting to the final step:
‘Add an IP Helper/DHCP Relay record to your router or switch so the DHCP broadcasts are sent to your normal DHCP server AND the Fog server.’
My router is the DHCP server, therefore it doesn’t allow you to provide a DHCP relay address without insisting it turns off the DHCP services… PAIN!
-
[quote=“rjn239, post: 31304, member: 24764”]Thanks for the alternative, seems like a good work around. Only problem is after implementing and getting to the final step:
‘Add an IP Helper/DHCP Relay record to your router or switch so the DHCP broadcasts are sent to your normal DHCP server AND the Fog server.’
My router is the DHCP server, therefore it doesn’t allow you to provide a DHCP relay address without insisting it turns off the DHCP services… PAIN![/quote]
That part is only required to server multiple subnets, for now focus on getting one of your networks working and look into the ip Helper later. I personally don’t use the ip Helpers. My other co workers set some up to help resolve to WDS and I want to use FOG, so I use DNSmasq to override their settings. I’ve never had an issue, but I realize it’s all about the network structure and the equipment.
-
[quote=“Jaymes Driver, post: 31422, member: 3582”]That part is only required to server multiple subnets, for now focus on getting one of your networks working and look into the ip Helper later. I personally don’t use the ip Helpers. My other co workers set some up to help resolve to WDS and I want to use FOG, so I use DNSmasq to override their settings. I’ve never had an issue, but I realize it’s all about the network structure and the equipment.[/quote]
Thank you, this has worked
