Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Tftp package doesn't work but found a workaround

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    50 Posts 7 Posters 28.2k Views
    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.
    • B
      bioterror
      last edited by

      Thanks for this, I found this hint useful.
      You don't need to reboot, you can also just say a command "/etc/rc.d/inetd onestart"

      1 Reply Last reply Reply Quote 0
      • C
        cruzades
        last edited by

        Thank you very much.. my TFTP server is now working..

        1 Reply Last reply Reply Quote 0
        • B
          Brad303
          last edited by

          Noticed the same issue and implemented the same solution.

          Frustrating 30 minutes, but I guess that's the way it goes when playing with RCs.

          I didn't this listed in the current issues, nor a way to report new ticket.  Can we get this added an save future users our headaches?

          Thanks for this great product!

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            I just committed an updated TFTP package for 2.0, though it requires a change I just committed to 2.0 also. So if you update to a snapshot tomorrow and then reinstall the package, the tftpd daemon should be started as expected via inetd.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              Hi guys, I applied this workaround following these steps :

              1. added additional line in /etc/inetd.conf
              2. rebooted the box, despite I read you can make it work with /etc/rc.d/inetd onestart

              And…. it doesn't work... to make it work I have to exec /etc/rc.d/inetd stop and then /etc/rc.d/inetd onestart and then it works.
              If I reboot I have to do the same things. Quite strange isn't it ?

              Kind regards.

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                drjee,

                Did you not see my post? update to a current snapshot, reinstall the tftp package and you do not need any workarounds, it just works as-is.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • ?
                  Guest
                  last edited by

                  Hello,

                  Yes sorry I saw it. I forgot to mention that I run on 2.0RC May 12th build and re-installed the tftp package. But still not working as-is.
                  Did I make something wrong ?

                  1 Reply Last reply Reply Quote 0
                  • jimpJ
                    jimp Rebel Alliance Developer Netgate
                    last edited by

                    Odd that it doesn't work for you, I can't seem to make it fail. As long as the TFTP package is installed, it's running tftp automatically and the proper entry is in /var/etc/inetd.conf
                    It survives reboots and firmware upgrades/package reinstalls without problems for me.

                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                    Need help fast? Netgate Global Support!

                    Do not Chat/PM for help!

                    1 Reply Last reply Reply Quote 0
                    • ?
                      Guest
                      last edited by

                      Quite strange… I uninstalled it and reinstalled it, still not working.
                      What is the difference between /var/etc/inetd.conf and /etc/inetd.conf ?
                      Cause workaround they find is adding a line to /etc/inetd.conf
                      After package install, I can see that a line for tftp is added to /var/etc/inetd.conf but it does not work... (I also checked that service was running and it is).
                      Only way to make it work for me is to add an entry to /etc/inetd.conf

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        /etc/inetd.conf is not used by pfSense 2.0. /var/etc/inetd.conf is used by the TFTP proxy (and TFTP package).

                        When inetd is setup and started from filter.inc, it uses /var/etc/inetd.conf

                        : ps uxawww | grep inetd
                        root   47253  0.0  0.3  9036  1508  ??  INs  Thu10AM   0:00.00 /usr/sbin/inetd -wW -R 0 -a 127.0.0.1 /var/etc/inetd.conf
                        : cat /var/etc/inetd.conf 
                        tftp-proxy      dgram   udp     wait            root    /usr/libexec/tftp-proxy tftp-proxy -v
                        tftp            dgram   udp     wait            root    /usr/libexec/tftpd      tftpd /tftpboot
                        

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • ?
                          Guest
                          last edited by

                          Thanks for your help.

                          Actually here is what I got on my side :

                          :ps uxawww | grep inetd
                          root   11514  0.0  0.6  3436  1400  ??  Ss    9:28PM   0:00.01 /usr/sbin/inetd -wW -C 60
                          
                          

                          Is there something that maybe wrong in my config for having not at all the same parameters behind /usr/sbin/inetd ?

                          1 Reply Last reply Reply Quote 0
                          • jimpJ
                            jimp Rebel Alliance Developer Netgate
                            last edited by

                            If you started it manually with /etc/rc.d/inetd, it will launch the wrong one.

                            Kill that process, then go to Status > Filter Reload, and force a filter reload with the button there, then check if the right one is running.

                            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                            Need help fast? Netgate Global Support!

                            Do not Chat/PM for help!

                            1 Reply Last reply Reply Quote 0
                            • ?
                              Guest
                              last edited by

                              Ok, sorry, the right one is now running, but tftp still not working.
                              Here is what I have in /var/etc/inetd.conf :

                              tftp-proxy      dgram   udp     wait            root    /usr/libexec/tftp-proxy tftp-proxy -v
                              19000   stream  tcp     nowait/0        nobody  /usr/bin/nc     nc -w 2000 192.168.1.236 25
                              19000   dgram   udp     nowait/0        nobody  /usr/bin/nc     nc -u -w 2000 192.168.1.236 25
                              19001   stream  tcp     nowait/0        nobody  /usr/bin/nc     nc -w 2000 192.168.1.235 80
                              19001   dgram   udp     nowait/0        nobody  /usr/bin/nc     nc -u -w 2000 192.168.1.235 80
                              19002   stream  tcp     nowait/0        nobody  /usr/bin/nc     nc -w 2000 192.168.1.235 443
                              19002   dgram   udp     nowait/0        nobody  /usr/bin/nc     nc -u -w 2000 192.168.1.235 443
                              19003   stream  tcp     nowait/0        nobody  /usr/bin/nc     nc -w 2000 192.168.1.13 3074
                              19003   dgram   udp     nowait/0        nobody  /usr/bin/nc     nc -u -w 2000 192.168.1.13 3074
                              19004   dgram   udp     nowait/0        nobody  /usr/bin/nc     nc -u -w 2000 192.168.1.13 88
                              19005   stream  tcp     nowait/0        nobody  /usr/bin/nc     nc -w 2000 192.168.1.234 3389
                              tftp            dgram   udp     wait            root    /usr/libexec/tftpd      tftpd /tftpboot
                              
                              
                              1 Reply Last reply Reply Quote 0
                              • jimpJ
                                jimp Rebel Alliance Developer Netgate
                                last edited by

                                : sockstat | grep inetd
                                root     inetd      47253 4  stream /var/run/check_reload_status
                                root     inetd      47253 6  stream /var/run/check_reload_status
                                root     inetd      47253 12 dgram  (not connected)
                                root     inetd      47253 13 udp4   *:*                   *:*
                                root     inetd      47253 17 udp4   127.0.0.1:6969        *:*
                                root     inetd      47253 18 udp4   127.0.0.1:69          *:*
                                

                                That last line is tftpd. You probably need to add a port forward on LAN for port udp/69 to direct it at 127.0.0.1:69, since inetd is only listening on localhost.

                                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                Need help fast? Netgate Global Support!

                                Do not Chat/PM for help!

                                1 Reply Last reply Reply Quote 0
                                • ?
                                  Guest
                                  last edited by

                                  Damn sorry…. still does not work, even after creation of nat+passing rule.
                                  May this be due to the fact that I have manual outbound nat ? (required for xbox live to work correctly)

                                  Here are sockstat results, it seems that tftp daemon is listening

                                  root     inetd      1883  4  stream /var/run/check_reload_status
                                  root     inetd      1883  6  stream /var/run/check_reload_status
                                  root     inetd      1883  12 dgram  (not connected)
                                  root     inetd      1883  13 udp4   *:*                   *:*
                                  root     inetd      1883  17 udp4   127.0.0.1:6969        *:*
                                  root     inetd      1883  18 tcp4   127.0.0.1:19000       *:*
                                  root     inetd      1883  19 udp4   127.0.0.1:19000       *:*
                                  root     inetd      1883  20 tcp4   127.0.0.1:19001       *:*
                                  root     inetd      1883  21 udp4   127.0.0.1:19001       *:*
                                  root     inetd      1883  22 tcp4   127.0.0.1:19002       *:*
                                  root     inetd      1883  23 udp4   127.0.0.1:19002       *:*
                                  root     inetd      1883  24 tcp4   127.0.0.1:19003       *:*
                                  root     inetd      1883  25 udp4   127.0.0.1:19003       *:*
                                  root     inetd      1883  26 udp4   127.0.0.1:19004       *:*
                                  root     inetd      1883  27 tcp4   127.0.0.1:19005       *:*
                                  root     inetd      1883  28 udp4   127.0.0.1:69          *:*
                                  
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • jimpJ
                                    jimp Rebel Alliance Developer Netgate
                                    last edited by

                                    manual outbound nat wouldn't affect it.

                                    Show me exactly what your port forward rule on LAN looks like.

                                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                    Need help fast? Netgate Global Support!

                                    Do not Chat/PM for help!

                                    1 Reply Last reply Reply Quote 0
                                    • ?
                                      Guest
                                      last edited by

                                      I just attached them.

                                      1.png
                                      1.png_thumb
                                      2.png
                                      2.png_thumb

                                      1 Reply Last reply Reply Quote 0
                                      • jimpJ
                                        jimp Rebel Alliance Developer Netgate
                                        last edited by

                                        Just do UDP, not tcp/udp.

                                        Also make sure you do NOT have the TFTP proxy set to listen on LAN (System > Advanced, Firewall/NAT tab).

                                        Next week some time I can add an interface selection to add the rules automatically, and warn if the proxy is on. They'd both be adding a rule redirecting port 69, so if one is active the other wouldn't work.

                                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                        Need help fast? Netgate Global Support!

                                        Do not Chat/PM for help!

                                        1 Reply Last reply Reply Quote 0
                                        • ?
                                          Guest
                                          last edited by

                                          Ok, I extended to TCP/UDP to see but now I set it back to UDP only.
                                          TFTP proxy is not listening on any interface.
                                          Still not working… I'm getting crazy :) anyway, thanks for your support

                                          1 Reply Last reply Reply Quote 0
                                          • jimpJ
                                            jimp Rebel Alliance Developer Netgate
                                            last edited by

                                            It looks right otherwise… I have no trouble pulling a test file from my VM with a port forward that looks like that.

                                            What do you get if you try this:

                                            : grep 'port 69' /tmp/rules.debug
                                            

                                            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                            Need help fast? Netgate Global Support!

                                            Do not Chat/PM for help!

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.