A guided TFTP Server recovery tool for macOS
If an OpenWrt-style router will not boot, first check the Mac IP, firmware file, Ethernet connection, TFTP Server folder, and recovery mode before sending firmware.
TFTP: a simple local file-transfer method. In recovery, the router may ask your Mac for one firmware file.
Recovery mode: a temporary rescue state used when the router cannot start normally. It usually exposes only the basics needed to accept firmware.
Bootloader: the small startup program that runs before the normal router system. Many recovery flows are controlled by it.
Static IP / same subnet: a temporary Mac address such as 192.168.1.254 so the Mac can talk to a router waiting in recovery mode.
What to do: check the router label and hardware revision, then download matching recovery firmware. Why: mismatched firmware is a common cause of failed recovery. You should see: a filename, model, and hardware revision that clearly match.
What to do: temporarily set the Mac Ethernet IP to the address required by the guide, such as 192.168.1.254. Why: this lets the Mac communicate with the router while it is in recovery mode. You should see: Ethernet connected, with the Mac IP and router recovery IP in the same local network range.
What to do: select the firmware file and let Router Recovery wait for the router request. Why: the router recovery window may be brief, so the Mac should be ready first. You should see: the app waiting for the router request or showing that a request was detected.
What to do: follow the model guide, usually power off, hold Reset or WPS, then power on. Why: the router must enter recovery mode before it can request or accept firmware. You should see: the documented LED pattern, a brief network response, or the app detecting a firmware request.
TFTP recovery is useful when a router no longer boots normally after a firmware flash, cannot reach LuCI, or waits for a firmware file during bootloader recovery. OpenWrt devices vary by model, so always confirm the device page and bootloader instructions before sending firmware.
Many workflows ask the computer and router to sit on the same local subnet. A common setup is router 192.168.1.1 and Mac 192.168.1.254 with subnet mask 255.255.255.0, but some brands use different addresses.
OpenWrt failsafe and recovery documentation often references 192.168.1.1. Treat it as a common starting point, not a universal promise. If your router model specifies another recovery IP, follow the model-specific value.
On macOS, set the Ethernet adapter to a manual IPv4 address in the same subnet. 192.168.1.254 avoids conflicting with the router address while keeping your Mac reachable during recovery.
Use the recovery image or factory image required by your model and hardware revision. Wrong files, wrong filenames, and archived files that were not extracted are common causes of failed recovery.
Choose the folder containing the firmware, start the TFTP server, connect Ethernet directly if possible, then power the router into recovery mode. The app helps prepare and run the TFTP environment; it does not guarantee every router can be recovered.
No. 192.168.1.1 is common in OpenWrt failsafe and many recovery workflows, but the recovery IP depends on the device and bootloader.
It places your Mac in the same subnet as a router using 192.168.1.1 while avoiding the router address itself.
No. It helps prepare and run the TFTP recovery environment. The actual flashing behavior depends on your router recovery mode.