TFTP Open Timeout Problems on New Debian 9 instance
-
Hello,
I’m very new to Linux but i’m attempting to set up a portable FOG Server on Debian 9.
I’ve followed the config video for Debian 8 and didn’t notice any major differences. However after the FOG Server installation is complete the Hosts receive a TFTP Open Timeout Error.
I am using a Cisco 4331 Router for DHCP, and have configured option 66 as the Fog Server IP & Option 67 as ascii undionly.kpxe
Firewall is disabled and permissions to folder are set to 777.
Help would be appreciated!
-
Found the problem! Hurrah!
Managed to find this page on other DHCP Settings for routers which listed instructions for Cisco: https://wiki.fogproject.org/wiki/index.php?title=Other_DHCP_Configurations
We initially used:
Option 66 [Server IP] Option 67 ascii undionly.kpxe
What actually worked
next-server <Server IP> bootfile undionly.kpxe
Thanks for the help @Sebastian-Roth @george1421
-
@Critchleyb Have you worked through this yet? https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP
-
Hi,
Yes I’ve been working through what I can understand.
using tftp -i [ip] get undionly.kpxe on the host returns the packet succesfully when the firewall is disabled. But not when it is enabled.
FTP_Username and FTP_Password are set to the fog user that was created during setup
I’ve disabled the Debian firewall and confirmed the output is:
Chain INPUT (policy ACCEPT)
target prot opt source destinationChain FORWARD (policy ACCEPT)
target prot opt source destinationChain OUTPUT (policy ACCEPT)
target prot opt source destinationand set the permissions using: chmod -R 777 /tftpboot
-
@Critchleyb Then tftp does not seen to run. What do you get from
ps aux | grep tftp
-
@Sebastian-Roth I’ll check first thing tomorrow morning when i’m back in the office and let you know.
-
@Sebastian-Roth said in TFTP Open Timeout Problems on New Debian 9 instance:
What do you get from ps aux | grep tftp ?
You might also want to try this check
netstat -an|grep 69
where the output should contain a few lines but the following one is important. If this line is missing then your tftp server is not available.udp 0 0 0.0.0.0:69 0.0.0.0:*
The above result shows that “something” is listening on udp port 69 which is what tftp server uses. The risk with the
ps
command is if tftpd is managed by xinetd the tftpd task won’t be running in memory until someone requests a file the xinetd will start up tftpd to chat with the client. -
Using that command i can see entries for the following that look like they match:
udp 0 0 0.0.0.0:69 0.0.0.0:* udp6 0 0 :::69 :::*
root@fog-server:/# ps aux | grep tftp root 12019 0.0 0.0 4724 780 pts/0 S+ 09:09 0:00 grep tftp root 26270 0.0 0.0 2820 952 ? Ss Nov21 0:00 /usr/sbin/in.tftpd --listen --user root --address :69 -s /tftpboot
This is what i get from your command.
It looks like the server is running, but cant be contacted when i’m booting through PXE?
-
Found the problem! Hurrah!
Managed to find this page on other DHCP Settings for routers which listed instructions for Cisco: https://wiki.fogproject.org/wiki/index.php?title=Other_DHCP_Configurations
We initially used:
Option 66 [Server IP] Option 67 ascii undionly.kpxe
What actually worked
next-server <Server IP> bootfile undionly.kpxe
Thanks for the help @Sebastian-Roth @george1421