• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

TFTP Open Timeout Problems on New Debian 9 instance

Scheduled Pinned Locked Moved Solved
Linux Problems
3
8
1.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C
    Critchleyb
    last edited by Nov 21, 2018, 5:06 PM

    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!

    1 Reply Last reply Reply Quote 0
    • C
      Critchleyb
      last edited by Critchleyb Nov 22, 2018, 3:42 AM Nov 22, 2018, 9:42 AM

      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

      1 Reply Last reply Reply Quote 2
      • S
        Sebastian Roth Moderator
        last edited by Nov 21, 2018, 5:12 PM

        @Critchleyb Have you worked through this yet? https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 1
        • C
          Critchleyb
          last edited by Nov 21, 2018, 5:30 PM

          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 destination

          Chain FORWARD (policy ACCEPT)
          target prot opt source destination

          Chain OUTPUT (policy ACCEPT)
          target prot opt source destination

          and set the permissions using: chmod -R 777 /tftpboot

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Nov 21, 2018, 5:51 PM

            @Critchleyb Then tftp does not seen to run. What do you get from ps aux | grep tftp

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            C G 2 Replies Last reply Nov 21, 2018, 6:03 PM Reply Quote 1
            • C
              Critchleyb @Sebastian Roth
              last edited by Nov 21, 2018, 6:03 PM

              @Sebastian-Roth I’ll check first thing tomorrow morning when i’m back in the office and let you know.

              1 Reply Last reply Reply Quote 0
              • G
                george1421 Moderator @Sebastian Roth
                last edited by george1421 Nov 21, 2018, 12:46 PM Nov 21, 2018, 6:44 PM

                @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.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                C 1 Reply Last reply Nov 22, 2018, 9:16 AM Reply Quote 1
                • C
                  Critchleyb @george1421
                  last edited by Nov 22, 2018, 9:16 AM

                  @george1421

                  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                   :::*
                  

                  @Sebastian-Roth

                  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?

                  1 Reply Last reply Reply Quote 0
                  • C
                    Critchleyb
                    last edited by Critchleyb Nov 22, 2018, 3:42 AM Nov 22, 2018, 9:42 AM

                    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

                    1 Reply Last reply Reply Quote 2
                    • 1 / 1
                    1 / 1
                    • First post
                      4/8
                      Last post

                    219

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project