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:guide-user:troubleshooting:tftpserver [2022/04/04 07:54] – added WARNING for TFTP-SERVER, added alternative option for macOS: pkg-mngr based packages/tools, also mentioned MacPorts based option for some tools, etc aterik | docs:guide-user:troubleshooting:tftpserver [2024/04/28 17:45] – Logical restructuring anf small fixes jalakas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Setting up a TFTP server for TFTP Recovery/Install ====== | + | ===== What is TFTP Recovery |
| - | __WARNING__ : TFTP server / protocol uses much lesser //(or almost no)// security, to make sure low level data transfer can occur easily between devices //(in the hand of user who have devices in front of him/her)//. So access to TFTP-Server ('' | + | On most devices, the vendor provides |
| - | + | ||
| - | + | ||
| - | ===== What is TFTP Recovery over Ethernet? ===== | + | |
| - | On most devices, the vendor provided boot loader is a partition separated from the actual firmware. In case of a failed flash process or in case of a misconfiguration, | + | There are two potential modes of operation: |
| - | For many routers the recovery works by starting a TFTP server on your computer. Then device with the broken firmware has to be started up in TFTP recovery | + | **1. TFTP recovery |
| - | Some devices do not have automatic pull function and they need manual | + | For many routers, the recovery process requires you to host the firmware image on a TFTP server on your computer. Then device with the broken firmware then has to be started up in TFTP recovery mode. Some devices then will automatically pull the network-provided |
| - | NOTE: Some other routers, e.g. many Netgear routers, | + | Other devices do not have automatic pull function |
| - | The below article mainly advises on the "TFTP client at router" | + | **2. TFTP recovery |
| + | Some other routers, e.g. many Netgear routers, run a TFTP server in recovery mode, and you need to upload the firmware to the device using a TFTP client. | ||
| - | ===== Is TFTP recovery | + | 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. |
| + | \\ | ||
| + | ===== Is TFTP Recovery | ||
| 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. | 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. | ||
| Note: | Note: | ||
| - | * Your device boot loader could alternatively have implemented TFTP recovery over [[: | + | ● Your device boot loader could alternatively have implemented TFTP recovery over [[: |
| - | | + | ● Your device could also have [[docs: |
| - | + | \\ | |
| ===== Setting up TFTP Recovery/ | ===== Setting up TFTP Recovery/ | ||
| Line 33: | Line 32: | ||
| - Set the IP address of your computer' | - Set the IP address of your computer' | ||
| - Start the TFTP server on your computer. | - Start the TFTP server on your computer. | ||
| - | - Connect your computer and your device with Ethewnet | + | - Connect your computer and your device with Ethernet |
| - | - Power up the router and press a device-specific button to start firmware recovery over TFTP, | + | - 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. |
| - | - 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/ | ||
| + | {{page> | ||
| + | Access to TFTP-client ('' | ||
| - | ===== Setting up TFTP Server ===== | + | If your computer is also used as a desktop computer for general purpose or for other purpose than build/ |
| + | * //(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)// | ||
| - | ==== On macOS ==== | + | 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 and TFTP-client both are completely disabled in your OS/distro : turn off TFTP-server service / process, disable TFTP-server startup script file, and **move** the TFTP-client |
| - | + | ||
| - | macOS provides a native tftpd server that runs the command line. However, it is not verified | + | |
| + | **<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 (on macOS): === | ||
| Dnsmasq can be installed easily via [[https:// | Dnsmasq can be installed easily via [[https:// | ||
| - | * Launch it in this way (if you use Homebrew pkg-mngr):< | ||
| - | * Launch it in this way (if you use MacPorts pkg-mngr):< | ||
| - | |||
| - | Replace '' | ||
| + | ● 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: === | === macOS Command-Line Native tftpd: === | ||
| For recent versions of macOS, the system-supplied '' | 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. | + | ● 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 cp path/ | ||
| - | $ sudo launchctl load -F / | + | $ sudo launchctl load -F / |
| - | + | ● Confirm '' | |
| - | * Confirm '' | + | |
| $ netstat -an | fgrep \*.69 | $ netstat -an | fgrep \*.69 | ||
| udp4 | udp4 | ||
| + | ● Activate your device' | ||
| + | * When done with '' | ||
| + | \\ | ||
| + | === TftpServer.app (on macOS): === | ||
| - | * Activate your device' | + | As an example of a GUI wrapper (aka: frontend) based TFTP server, |
| - | * When done with '' | + | * This procedure was tested with '' |
| - | + | * The v3.4.1 '' | |
| - | + | * Author' | |
| - | === TFTPServer.app on macOS: === | + | |
| - | + | ||
| - | As an example of a GUI-driven | + | |
| - Download '' | - Download '' | ||
| Line 86: | Line 95: | ||
| - //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): === | ||
| + | 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): === | === Tools/Pkgs via Pkg-Mngr (on macOS): === | ||
| - | macOS compatible // | + | macOS compatible // |
| - | if you have MacPorts pkg-mngr, then run**:** <code bash> | + | if you have MacPorts pkg-mngr, then run**:** <code bash> |
| * the '' | * 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. | ||
| - | ==== On Windows ==== | + | The built-in client tftp feature can be installed from an administrator cmd.exe |
| - | + | \\ | |
| - | While there is a command | + | Regardless of which TFTP server below that you choose |
| - | + | < | |
| + | \\ | ||
| === Tftpd64 (on Windows): === | === Tftpd64 (on Windows): === | ||
| Line 109: | 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 |
| - | 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/ | + | 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/ | ||
| Click on the drop-down menu called **Server Interfaces** and select your PC's Ethernet port. | 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. | Now the TFTP server is online and ready, and the file(s) in it can be accessed as normal. | ||
| - | + | \\ \\ | |
| === Tiny PXE (on Windows): === | === Tiny PXE (on Windows): === | ||
| [[http:// | [[http:// | ||
| + | \\ \\ | ||
| + | === Solarwinds TFTP Server === | ||
| + | A free TFTP server for Windows can be downloaded [[https:// | ||
| - | ==== On Linux ==== | + | * 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 (on Linux): === | + | **dnsmasq** is pre-installed in most distributions. |
| - | **Dnsmasq** is pre-installed in most distributions. | + | Create directory where you want to put the recovery |
| - | Put an image file into your directory - actual name will vary. | + | bash# |
| - | Then run TFTP server:<code bash> | + | |
| - | # dnsmasq --port=0 --enable-tftp --tftp-root=/path/to/ | + | |
| - | Check if your TFTP server is listening: | + | |
| - | # netstat -lunp | grep 69</ | + | |
| + | Put an image file into your directory - actual name will vary: <code bash> | ||
| + | bash# cp ~/ | ||
| - | === atftpd (on Linux): === | + | 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**: | You can also use **atftpd**: | ||
| <columns 100% 50% - -> | <columns 100% 50% - -> | ||
| - | Install atftpd from repository on Debian/ | + | Install atftpd from repository on Debian/ |
| - | # apt install atftpd | + | bash# apt install atftpd |
| < | < | ||
| - | Install atftpd from repository on RedHat/ | + | Install atftpd from repository on RedHat/ |
| - | # yum install atftpd | + | bash# yum install atftpd |
| </ | </ | ||
| - | Create directory where you want to put the image file <code bash> | + | Create directory where you want to put the recovery |
| - | # mkdir /srv/tftp </ | + | bash# |
| - | Put an image file into your directory - actual name will vary < | + | |
| - | | + | |
| - | Change the ownership of the folder and the file in it <code bash> | + | |
| - | # chown nobody: | + | |
| - | Run TFTP server (run as daemon, do not fork, log events to stdout) <code bash> | + | |
| - | # atftpd --daemon --no-fork --logfile - /srv/tftp </ | + | |
| - | Check if your TFTP server is listening <code bash> | + | |
| - | # netstat -lunp|grep 69 </ | + | |
| - | * //If not set, you should try running TFTP server as superuser.// | + | |
| + | 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: | ||
| + | |||
| + | Run TFTP server (run as daemon, do not fork, log events to stdout): <code bash> | ||
| + | bash# atftpd --daemon --no-fork --logfile - /srv/tftp </ | ||
| + | |||
| + | Check if your TFTP server is listening: <code bash> | ||
| + | bash# netstat -lunp|grep 69 </ | ||
| + | * //If not set, you should try running TFTP server as superuser.// | ||
| + | \\ | ||
| + | === Testing TFTP server (on Linux): === | ||
| - | ==== Testing TFTP server ==== | ||
| **Check that you can in fact pull the file from your TFTP server.** | **Check that you can in fact pull the file from your TFTP server.** | ||
| - | Preferably from another computer call your TFTP server IP: (//or if not possible, in same server call IP 0.0.0.0// | + | Preferably from another computer call your TFTP server IP: (//or if not possible, in same server call IP 0.0.0.0//): <code bash> |
| - | # tftp 192.168.0.66 | + | bash# tftp 192.168.0.66 |
| - | tftp> get tp_recovery.bin | + | tftp> get tp_recovery.bin |
| - | Received 8152633 bytes in 0.8 seconds | + | Received 8152633 bytes in 0.8 seconds |
| - | tftp> quit | + | tftp> quit </ |
| If you have received the file, congratulations, | If you have received the file, congratulations, | ||
| + | \\ \\ | ||
| + | ===== Troubleshooting steps ===== | ||
| - | |||
| - | ===== Troubleshooting ===== | ||
| TFTP file transfer doesn' | TFTP file transfer doesn' | ||
| * Check if your TFTP server is running and listening | * Check if your TFTP server is running and listening | ||
| Line 179: | Line 225: | ||
| * Check if server IP is set correctly | * Check if server IP is set correctly | ||
| * Make sure server firewall allows inbound TFTP on UDP port 69 | * 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: | 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 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/ | * Try using alternate cable, a crossover cable or alternate switch/ | ||
| * Try connecting to an alternate port on the router / routers switch | * Try connecting to an alternate port on the router / routers switch | ||
| Line 189: | Line 238: | ||
| * Try an alternate server software, client software or TFTP transfer mode | * 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... | * 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:// | ||