TFTP Problem, Ubuntu 14.04 Fog 1.2.0 server on isolated network

[Wayne Workman]

I think it’s DHCP related.

Make sure it’s running. give it a restart too.

service dhcpd status
service dhcpd restart

If it’s running with no errors, do a Wireshark capture to see if the DHCP server is giving out the options properly. Feel free to post the capture file (the .pcap file) here for others to look at.

[ITSolutions]

@Wayne-Workman I think you maybe right now that I look at his dhcpd.conf file a little closer I noticed option tftp-server-name line in his config. I have run into issues in the past with this. @stan6595 Can you try removing, or remarking this line out and restart your DHCP and see if that works for you? service dhcpd restart

Not a guarantee, but like I said I have seen where it can be an issue. The next-server should be fine for passing the option to the client.

[Wayne Workman]

@ITSolutions Ah I didn’t see that. Nice catch.

[stan6595]

Thank you guys

@Wayne-Workman

Here is the file from the WireShark from the very beginning of the connect to “Network Not Found” display on the screen

FogCapture.pcapng

@ITSolutions

I tried your methods, I mark out the line of option tftp-server-name. As a result, “TFTP timeout-PXE-E32” display on the screen and “Network Not Found” display on the screen

[Tom Elliott]

It seems that the problem is the way you’re trying to start tftp. Ubuntu usually uses tftpd-hpa, not xinetd.

Try:

sudo service tftpd-hpa stop; sleep 2; sudo service tftpd-hpa start

[Wayne Workman]

Can you try this for you ISC-DHCP configuration and see what happens?

option space PXE;
option PXE.mtftp-ip    code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 192.168.1.1;
authoritative;


subnet 192.168.1.0 netmask 255.255.255.0 {
        option subnet-mask              255.255.255.0;
        range dynamic-bootp 192.168.1.10 192.168.1.254;
        default-lease-time 21600;
        max-lease-time 43200;
        option domain-name-servers      192.168.1.1;
	#option routers      x.x.x.x;
 
    class "UEFI-32-1" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
    filename "i386-efi/ipxe.efi";
    }

    class "UEFI-32-2" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
     filename "i386-efi/ipxe.efi";
    }

    class "UEFI-64-1" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
     filename "ipxe.efi";
    }

    class "UEFI-64-2" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
    filename "ipxe.efi";
    }

    class "UEFI-64-3" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
     filename "ipxe.efi";
    }

    class "Legacy" {
    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
    filename "undionly.kkpxe";
    }

    }

[Sebastian Roth]

In the packet dump I can see ‘Fragmented IP Protocol’ which means that the TFTP packets seam to be too big in your network. Usually ethernet has an MTU of 1500 and the blocksize of 1456 used here shouldn’t cause a problem. But somehow it does!

Give this a try: Edit /etc/default/tftp-hpa and add the blocksize option

...
TFTP_OPTIONS="-s --blocksize=512"

512 is very small but should hopefully work for you. If it does you can crank it up step by step. By the way, what kind of network is this?

[Trevelyan]

Random other suggestion; check /tftpboot folder, see if undionly.0 exists. If it doesn’t, try this as root:

cd /tftpboot

sudo su

ln -r -s undionly.kpxe undionly.0

[stan6595]

Hello, Everyone.

Here comes the update

I tried to restart the tftp whcih @Tom Elliott mentioned below.
I did edit my dhcp config just the exactly the same as @Wayne-Workman 's reply below.
And I also add one more line refer from @Uncle-Frank 's reply below.

I tried those methods separately, but didn’t work out well.

However, when I combine those methods together. Fog server finally run and I can upload and download images to the machine now.

Thank you everyone who contributes in this post.

Note: there is a login fail problem with this particular setting. To resolve this issue, change your password through the database to modify your password.

[Wayne Workman]

@stan6595 Thank you for following up!

If you have any other problems, never hesitate to start a new thread! (search for a solution first though)