Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:user-guide:troubleshooting:tftpserver [2018/02/22 04:57] – [TFTP Server on Mac OSX] jeff | docs:guide-user:troubleshooting:tftpserver [2024/04/28 17:45] – Logical restructuring anf small fixes jalakas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Set up a TFTP Server ====== | + | ===== What is TFTP Recovery over Ethernet? |
| - | LEDE firmware | + | On most devices, the vendor provides a boot loader on a discreet partition that is untouched by firmware |
| - | - Download the desired LEDE (or stock) firmware image to the designated TFTP directory on your computer | + | There are two potential modes of operation: |
| - | - Set the IP address | + | |
| - | - Start the TFTP server on your computer. | + | |
| - | - Power up the router and press the specified button. | + | |
| - | This page gives instructions for setting up a TFTP server on your computer that can supply the image for recovery. | + | **1. TFTP recovery |
| - | ===== TFTP Server | + | For many routers, the recovery process requires you to host the firmware image on a TFTP server |
| - | macOS provides a native tftpd server that runs the command line. There are also GUI applications that are available for those that prefer them. | + | Other devices do not have automatic pull function and they need you to manually TFTP copy commands in recovery mode to download |
| - | ==== Command-Line Native tftpd ==== | + | **2. TFTP recovery server** |
| - | For recent versions of macOS, the system-supplied '' | + | Some other routers, e.g. many Netgear routers, run a TFTP server in recovery mode, and you need to upload |
| - | * Configure your network interface for the proper server address for your device. Using System Preferences > Network is perhaps the easiest. | + | The below article mainly advises on the first mode of recovery, i.e. the router runs a TFTP client and you need to host the firmware image on a TFTP server. |
| - | * Connect your device | + | \\ |
| - | * Start '' | + | ===== Is TFTP Recovery over Ethernet supported by my device? ===== |
| - | $ sudo cp path/ | + | TFTP recovery over Ethernet is not supported by every router model. TFTP recovery is based on a device- and vendor-specific boot loader that may or may not be present on your device. Check the OpenWrt device page for your precise model to find out, if your device has a boot loader supporting TFTP recovery. If your device supports it, then this recovery function will still be present in your device boot loader, after OpenWrt firmware has been flashed onto the device. |
| - | $ sudo launchctl load -F / | + | |
| - | * Confirm '' | + | Note: |
| + | ● Your device boot loader could alternatively have implemented TFTP recovery over [[: | ||
| + | ● Your device could also have [[docs: | ||
| + | \\ | ||
| + | ===== Setting up TFTP Recovery/ | ||
| - | $ netstat | + | The following procedure only describes how to set up a TFTP server over Ethernet for the TFTP recovery/ |
| - | udp4 | + | |
| + | - Download the desired OpenWrt (or stock) firmware image to the designated TFTP directory on your computer (and rename it if needed). | ||
| + | - Set the IP address of your computer' | ||
| + | - Start the TFTP server on your computer. | ||
| + | - Connect your computer and your device with Ethernet cable. | ||
| + | - Power up the router and press a device-specific button to start firmware recovery over TFTP, or access boot loader recovery options and install recovery firmware over TFTP. | ||
| + | - Stop the TFTP server on your computer | ||
| + | \\ | ||
| + | ==== Setting up a TFTP server for TFTP Recovery/ | ||
| - | * Activate your device's recovery/TFTP mode | + | {{page> |
| - | * When done with '' | + | Access to TFTP-client ('' |
| - | $ sudo launchctl unload | + | If your computer is also used as a desktop computer for general purpose or for other purpose than build/ |
| - | ==== TFTPServer.app ==== | + | * //(frwl rule # 1)// allow TFTP traffic (UDP 69) only when connections originate from a local LAN ip.address range and also end in the local LAN ip.address range |
| + | * //(frwl rule # 2)// TFTP traffic is Not-Allowed when it is from/to '' | ||
| + | * //(frwl rule # 3)// TFTP traffic is Not-Allowed when originated from Internet-ip-address //(aka: NON private-LAN ip-address ranges)// | ||
| - | As an example of a GUI-driven tftp server, TFTPServer.app from http://ww2.unime.it/flr/tftpserver/ provides | + | And you must also make sure to do this: after your develop / troubleshooting etc work is done or when you pause to goto other work, then make sure the TFTP-server |
| - | | + | **<color # |
| + | \\ \\ | ||
| + | ==== Setting up a TFTP server on macOS ==== | ||
| + | |||
| + | macOS provides a native tftpd server that runs the command line. However, it is not verified to work on recent versions (10.15.x). So alternative option-1 is: use '' | ||
| + | \\ \\ | ||
| + | === dnsmasq (on macOS): === | ||
| + | |||
| + | Dnsmasq can be installed easily via [[https:// | ||
| + | |||
| + | ● Launch it in this way (if you use Homebrew pkg-mngr): <code bash> $ sudo / | ||
| + | ● Launch it in this way (if you use MacPorts pkg-mngr): <code bash> $ sudo / | ||
| + | |||
| + | Replace '' | ||
| + | \\ \\ | ||
| + | === macOS Command-Line Native tftpd: === | ||
| + | |||
| + | For recent versions of macOS, the system-supplied '' | ||
| + | |||
| + | ● Configure your network interface for the proper server address for your device. Using System Preferences > Network is perhaps the easiest. | ||
| + | ● Connect your device to the network interface. | ||
| + | ● Start '' | ||
| + | $ sudo cp path/ | ||
| + | $ sudo launchctl load -F / | ||
| + | ● Confirm '' | ||
| + | $ netstat -an | fgrep \*.69 | ||
| + | udp4 | ||
| + | ● Activate your device' | ||
| + | * When done with '' | ||
| + | \\ | ||
| + | === TftpServer.app (on macOS): === | ||
| + | |||
| + | As an example of a GUI wrapper (aka: frontend) based TFTP server, the '' | ||
| + | * This procedure was tested with '' | ||
| + | * The v3.4.1 '' | ||
| + | * Author' | ||
| + | |||
| + | - Download '' | ||
| - Move the application to a convenient directory. | - Move the application to a convenient directory. | ||
| - In the same directory, create another folder named ' | - In the same directory, create another folder named ' | ||
| Line 48: | Line 94: | ||
| - Start your router and press the button. //The file will transfer.// | - Start your router and press the button. //The file will transfer.// | ||
| - //Note:// TftpServer.app may give warnings about file permissions. Use the " | - //Note:// TftpServer.app may give warnings about file permissions. Use the " | ||
| - | - Click "Stop TFTP" or quit the application to stop the TFTP server. | + | - Click "Stop TFTP" or quit the application to stop the TFTP server. |
| + | - Precautions : keep this app firewalled //(and allow only LAN based TFTP)//, or disable this app when you are done working with TFTP, or disable this app when you pause to goto other work. Do not keep this app continuously running. | ||
| + | \\ | ||
| + | === PumpKIN.app (on macOS): === | ||
| - | ===== TFTP Server | + | This app '' |
| + | * It is developed by Michael Krelin ( // | ||
| + | * The '' | ||
| + | * Precautions : keep this app firewalled //(and allow only LAN based TFTP)//, or disable this app when you are done working with TFTP, or disable this app when you pause to goto other work. Do not keep this app continuously running. | ||
| + | \\ | ||
| + | === Tools/Pkgs via Pkg-Mngr (on macOS): | ||
| - | While there is a command line TFTP server/client feature | + | macOS compatible |
| - | A simple and free TFTP application is **Tftpd32**, available [[http:// | + | if you have MacPorts pkg-mngr, then run**:** <code bash> $ sudo port install inetutils dnsmasq </ |
| + | * the '' | ||
| + | \\ | ||
| + | ==== Setting up a TFTP server on Windows ==== | ||
| + | |||
| + | While there is a command line TFTP **client** feature in Windows, Microsoft has stopped shipping a tftp **server** for security reasons. A third party tftp server will therefore be required. | ||
| + | |||
| + | The built-in client tftp feature can be installed from an administrator cmd.exe command prompt as follows: < | ||
| + | \\ | ||
| + | Regardless of which TFTP server below that you choose to use, you will need to open a local firewall rule to allow inbound client TFTP connections from the local subnet. For security reasons, only traffic from the local LAN subnet should be allowed. Start a cmd.exe prompt as admin then run: | ||
| + | < | ||
| + | \\ | ||
| + | === Tftpd64 (on Windows): === | ||
| + | |||
| + | A simple and free TFTP application is **Tftpd64**, available [[http:// | ||
| Download the portable version, and unzip it in a folder. You should see the manual, a license in a PDF file, a configuration file, and the application executable itself. | Download the portable version, and unzip it in a folder. You should see the manual, a license in a PDF file, a configuration file, and the application executable itself. | ||
| Line 60: | Line 128: | ||
| Place the file you want to send (the firmware file usually) in the same folder where you find the **Tftpd64** program file. The folder exposed through TFTP can be changed by clicking on Browse button, but in most situations you don't need to do that. | Place the file you want to send (the firmware file usually) in the same folder where you find the **Tftpd64** program file. The folder exposed through TFTP can be changed by clicking on Browse button, but in most situations you don't need to do that. | ||
| - | Configure your ethernet | + | Configure your Ethernet |
| + | |||
| + | This application might stop listening on the local UDP port at the very moment that you need it, i.e. when the router at the other end of the network connection restarts. To work around this issue, do one of the following: | ||
| + | * Disable [[https:// | ||
| + | netsh interface ipv6 set global dhcpmediasense=disabled</ | ||
| + | * Use a switch between the TFTP host and the client router so that the network link of the Windows machine remains up while the router is rebooting. | ||
| + | |||
| + | Double-click on the **Tftpd64** program file and you should get a Windows Firewall popup asking you to grant access. Check both options, to allow **Tftpd64** to communicate over both home/work but //not// public networks. This is very important, if the Windows Firewall blocks your TFTP server you won't be able to access it from the device you want to recover. | ||
| + | |||
| + | Click on the drop-down menu called **Server Interfaces** and select your PC's Ethernet port. | ||
| + | |||
| + | Now the TFTP server is online and ready, and the file(s) in it can be accessed as normal. | ||
| + | \\ \\ | ||
| + | === Tiny PXE (on Windows): === | ||
| + | |||
| + | [[http:// | ||
| + | \\ \\ | ||
| + | === Solarwinds TFTP Server === | ||
| + | |||
| + | A free TFTP server for Windows can be downloaded [[https:// | ||
| + | |||
| + | * The default install will use the directory '' | ||
| + | * Under File | Configure | Security, set "Send files" as the only permissible action. | ||
| + | * Change the local LAN IP address of your computer to the static IP that your router expects. | ||
| + | * Follow the procedure for your specific router to trigger its TFTP client to download the firmware image you are hosting. | ||
| + | * Watch the Solarwinds console to ensure that the router has downloaded the firmware file. | ||
| + | |||
| + | <color # | ||
| + | < | ||
| + | sc config " | ||
| + | sc stop " | ||
| + | </ | ||
| + | \\ | ||
| + | ==== Setting up a TFTP server on Linux ==== | ||
| + | === dnsmasq (on Linux): === | ||
| + | |||
| + | **dnsmasq** is pre-installed in most distributions. | ||
| + | |||
| + | Create directory where you want to put the recovery image file: <code bash> | ||
| + | bash# mkdir /srv/tftp </ | ||
| + | |||
| + | Put an image file into your directory - actual name will vary: <code bash> | ||
| + | bash# cp ~/ | ||
| + | |||
| + | Run TFTP server: <code bash> | ||
| + | bash# dnsmasq --listen-address=0.0.0.0 --port=0 --enable-tftp --tftp-root=/ | ||
| + | |||
| + | Check if your TFTP server is listening: <code bash> | ||
| + | bash# netstat -lunp | grep 69 </ | ||
| + | \\ | ||
| + | === atftpd (on Linux): === | ||
| + | |||
| + | You can also use **atftpd**: | ||
| + | <columns 100% 50% - -> | ||
| + | Install atftpd from repository on Debian/ | ||
| + | bash# apt install atftpd </ | ||
| + | < | ||
| + | Install atftpd from repository on RedHat/ | ||
| + | bash# yum install atftpd </ | ||
| + | </ | ||
| + | |||
| + | Create directory where you want to put the recovery image file: <code bash> | ||
| + | bash# mkdir /srv/tftp </ | ||
| + | |||
| + | Put an image file into your directory - actual name will vary: <code bash> | ||
| + | bash# cp ~/ | ||
| + | |||
| + | Change the ownership of the folder and the file in it: <code bash> | ||
| + | bash# chown nobody: | ||
| - | Double-click on the **Tftpd64** program file and you should get a Windows Firewall popup asking you to grant access. Check both options, to allow **Tftpd64** to communicate over both home/work and public networks. This is very important, if the Windows Firewall blocks your TFTP server | + | Run TFTP server |
| + | bash# atftpd --daemon --no-fork --logfile - /srv/tftp </ | ||
| - | Click on the drop-down menu called | + | Check if your TFTP server is listening: <code bash> |
| + | bash# netstat | ||
| + | | ||
| + | \\ | ||
| + | === Testing TFTP server (on Linux): === | ||
| - | Now the tftp server is online and ready, and the file(s) in it can be accessed as normal. | + | **Check that you can in fact pull the file from your TFTP server.** |
| - | ===== TFTP Server on Linux ===== | + | Preferably from another computer call your TFTP server IP: (//or if not possible, in same server call IP 0.0.0.0//): <code bash> |
| + | bash# tftp 192.168.0.66 | ||
| + | tftp> get tp_recovery.bin | ||
| + | Received 8152633 bytes in 0.8 seconds | ||
| + | tftp> quit </ | ||
| + | If you have received the file, congratulations, | ||
| + | \\ \\ | ||
| + | ===== Troubleshooting steps ===== | ||
| - | //This section needs to be written by someone who has used the procedure.// | + | TFTP file transfer doesn' |
| + | * Check if your TFTP server is running and listening | ||
| + | * Check if TFTP folder is set up correctly (location, access rights) | ||
| + | * Check if firmware file is set up correctly (location, access rights) | ||
| + | TFTP file transfer works from local computer, but not from another computer: | ||
| + | * Check if network cable is connected properly | ||
| + | * Check if server IP is set correctly | ||
| + | * Make sure server firewall allows inbound TFTP on UDP port 69 | ||
| + | * Check that you have opened up UDP 69 traffic from the local subnet in the host firewall. | ||
| + | * Restart the server if you have just changed the local host IP address. | ||
| + | TFTP file transfer works from another computer, but not from router: | ||
| + | * Check if server IP is set correctly (same as router is searching for) | ||
| + | * Check that the host running the TFTP server is using the specific fixed IP address and subnet mask that your router is expecting to use. | ||
| + | * Try using alternate cable, a crossover cable or alternate switch/speed | ||
| + | * Try connecting to an alternate port on the router | ||
| + | * Pay attention | ||
| + | * Verify the arp cache on either host... server side is easier... | ||
| + | * Use arp -s to add a static mapping or arp -d to delete stale entries... | ||
| + | * Use a third host to simply ping the router, both with static addresses if possible | ||
| + | * Try an alternate server software, client software or TFTP transfer mode | ||
| + | * If you get some activity, timing can often yield results, power cycle the router and start the transfer earlier or later... | ||
| + | * Check that you have downloaded a firmware image that contains " | ||
| + | * Run a packet sniffing tool like [[https://www.wireshark.org/ | ||