TFTP Open Timeout
-
Hello,
I’m back with a new question!
I’m running Fog alongside my DHCP server (Windows Server 2012) and for some reason, TFTP keeps timing out at PXE boot.
I’ve captured traffic using Wireshark and it looks something like this:
Server sends data packet “Block 0” to client
Client tells server “Fragemented IP protocol”Server sends data packet “Block 1” to client
Client tells server “Acknowledgement, Block: 0”And this repeats until it times out. Just sending block 0 and 1 back and forth.
I’m completely lost and any help would be greatly appreciated!
Thanks!
-
Alright, I’ve managed to clear this up by setting option 60 of my DHCP server to “PXEClient.”
The only issue now is that the computers get stuck at getting a DHCP address.
The weird thing is: a VM will pxeboot just fine but my physical machines wait for a DHCP address that they never get.
Again, I’m running Fog on Ubuntu 10.04 and on a separate machine, I’m running my DHCP server on Windows Server 2012.
*EDIT: Anything on the same subnet as the fog server will get DHCP fine. Anything outside of that subnet will not. I’ve tried to configure dnsmasq by doing: “dhcp-range=IP of my Fog Server,proxy,255.0.0.0” with no luck.
-
sounds like a problem I’ve encountered before (when I upgraded my Ububntu to 13.04) appears to be the the tftp service starts when the network isn’t up and can’t bind to any interfaces( anybody let me know if I’m wrong) by changing the start up script you can delay the service initializing until the network is up.
edit (nano or vi) " /etc/default/tftpd-hpa " and add “sleep 30” on the top line so it looks like :
[I][B]sleep 30[/B][/I]
[I][B]# /etc/default/tftpd-hpa[/B][/I]
[I][B]# FOG Modified version[/B][/I]
[I][B]TFTP_USERNAME=“root”[/B][/I]
[I][B]TFTP_DIRECTORY=“/tftpboot”[/B][/I]
[I][B]TFTP_ADDRESS=“0.0.0.0:69”[/B][/I]
[I][B]TFTP_OPTIONS=“-s”[/B][/I]will have to restart the service or reboot
let me know how you get on - should work though
also confirm that option 66 & 67 on your dhcp scope/server option points to your sog server (option 66) and “pxelinux.0” ( zero, for option 67)
-
Yup, my DHCP options 66 and 67 are set correctly. I can try to “sleep 30” and see what happens but if that was the case (that TFTP starts too early), wouldn’t I not be able to PXE boot into Fog at all?
I can PXE boot into Fog if I’m on the same subnet as the Fog server.
I cannot PXE boot into Fog if I’m on a different subnet as the Fog server.Either way, I’ll try in the morning and post how it went!
Thanks!
-
pxe from different subnet is ok - one way to quickly confirm is do a ps -A |grep tftp to see if its running if it is running but no process id then certainly try the sleep - let me know in the morning… will be evening for me
-
I just remoted in and ran “ps -A | grep tftp” and I get back nothing. I guess I’ll try the “sleep 30” tomorrow.
I’ll keep you posted!
-
Well, unfortunately the sleep 30 did not make a difference. Instead of waiting until morning, I remoted into my work PC, which remoted into an old imaging server, which remoted into a computer on a different subnet that had VMware Workstation on it.
Even with the sleep 30, Fog is still not working for other subnets outside of its own.
-
just check to see if the process is running again on the linux box “ps -A |grep tftp” if still not running check the logs /var/log on ubuntu
:$ ps -A |grep tftp
1184 ? 00:00:00 in.tftpd -
The service is still not running. ps -A|grep tftp comes back with nothing.
I tried to find a log in /var/log that looked like tftp but I could not find one.
-
nothing in syslog … can you post the syslog ?
-
Syslog says this:
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: error 0 TFTP Aborted received from 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: failed sending /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/c9a90b22-2b83-11dc-9346-00e01$
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/01-00-07-e9-1a-82-98 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786429 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78642 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7864 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/vesamenu.c32 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/fog/bg.png to 10.120.100.41 -
so it is proceesing the requests ok - try adding a simple task like mem test or inventory - should all work ok but to get it to boot local have a look at this [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url] - can you post the default file /tftpboot/pxelinux.cfg/default
-
Here is /tftpboot/pxelinux.cfg/default:
DEFAULT vesamenu.c32
MENU TITLE FOG Computer Cloning Solution
MENU BACKGROUND fog/bg.png
MENU MASTER PASSWD $1$0123456789
\n
menu color title 1;36;44 #ffffffff #00000000 std
\n
LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT
\n
LABEL fog.memtest
kernel fog/memtest/memtest
MENU LABEL Run Memtest86+
TEXT HELP
Run Memtest86+ on the client computer.
ENDTEXT
\n
LABEL fog.reg
MENU LABEL Quick Host Registration and Inventory
TEXT HELP
Automatically register the client computer,
and perform a hardware inventory.
ENDTEXT
\n
LABEL fog.reginput
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mode$
MENU LABEL Perform Full Host Registration and Inventory
TEXT HELP
Perform a full host registration on the client
computer, perform a hardware inventory, and
optionally image the host.
ENDTEXT
\n
LABEL fog.quickimage
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Quick Image
TEXT HELP
This mode will allow you to image this host quickly with
it’s default assigned image.
ENDTEXT
\n
LABEL fog.sysinfo
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Client System Information
TEXT HELP
View basic client information such as MAC address
and FOG compatibility.
ENDTEXT
LABEL fog.debug
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Debug Mode
TEXT HELP
Debug mode will load the boot image and load a prompt so
you can run any commands you wish.
ENDTEXT
\n
PROMPT 0
TIMEOUT 30\n -
just try updating PXELINUX as described [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url]
-
I did. It had no effect.
-
On the subnet where I have my Fog server setup, it PXE boots just fine. On any other subnet, it will not get a DHCP address which leads it to be unable to PXE boot.
-
so if that subnet isn’t getting dhcp - is there a scope set on the windows box for that subnet with a pool set - is the pool exhausted ? check to see if the pool isn’t exhausted …
-
i was under the impression it was getting an ip address ??? you syslog post [B]“sent /tftpboot/fog/bg.png to 10.120.100.41” [/B]
right ?[B][/B]
-
also check to make sure you are able to route to your fog server …
-
firewall rules ???