tftp issue

[Tom Elliott]

What is the contents of your tftpd-hpa file?

[belac]

@Tom-Elliott

here is the contents of the tftpd-hpa file from my fog server:

/etc/default/tftpd-hpa

FOG Modified version

TFTP_USERNAME=“root”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“:69”
TFTP_OPTIONS=“-s”

@Wayne
I have two windows vm’s running on a vmware cluster, same subnet, that i use to create images. both are win7. from the one vm i run the tftp test referenced in that article and it succeeds.

tftp is running on the fog server, and other systems are able to pxe boot. i also disabled the firewall.

[Tom Elliott]

@belac What happens if you run sudo service tftpd-hpa restart

[belac]

@Tom-Elliott the service sops and then starts.

[Wayne Workman]

@belac said:

other systems are able to pxe boot.

The system that cannot network boot with FOG, this is the one you tested getting the boot file via TFTP with?

Do you have dual DHCP servers running? Have you checked for IP conflicts for that one problematic host and with the FOG server?

[belac]

@Wayne-Workman what ip is supposed to be there, in the tftpd-hpa file? the article says 0.0.0.0, is that correct?

[Wayne Workman]

@belac Yes it’s correct as far as I am aware.

[Tom Elliott]

0.0.0.0 just means to use any interface.

I believe just :69 means to use anything, so even if network is not up when it starts, it won’t crash simply because network does come up.

[belac]

I was able to work around the issue. I had to migrate the trouble vm to the same host fog was running on and disable the second nic on the dhcp server (while pxe booting it was grabbing the ip of the second nic, not sure why).

thanks for the help guys.

[Wayne Workman]

@Tom-Elliott said:

0.0.0.0 just means to use any interface.

I believe just :69 means to use anything, so even if network is not up when it starts, it won’t crash simply because network does come up.

WiKi updated to reflect this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP#Ubuntu: