OPENWRT 24.10 EOL · SEPTEMBER 2026

OpenWrt 24.10 EOL: Should You Upgrade to 25.12?

September 2026 is the final planned support month for OpenWrt 24.10, not a reason to rush a blind upgrade. As verified September 1, 24.10.8 remains old-stable and 25.12.5 remains stable. Check the exact device, migration exception, configuration plan, and recovery evidence before moving.

Prepare OpenWrt Recovery on Mac View recovery checklist

Paid macOS app · View local pricing in the Mac App Store. Recovery checks run on your Mac, not on this page.

Browsing on your phone? Open this on your Mac later

Copy this link and send it to your Mac using your preferred method.

Verified September 1, 2026: 24.10.8 remains old-stable and 25.12.5 remains stable. September is the final planned support month, not permission to upgrade every device without conditions.

READ THE ACTUAL RELEASE STATE FIRST

Combine EOL urgency with device migration risk

Firmware releases, package feeds, and device migration notes are separate evidence. Continue only when all three are understood.

OpenWrt release state · 2026-09-01

From official release pages, release notes, and download directories—not live device detection.

OpenWrt 24.10.8 Current old-stable; security updates are planned to end after September 2026 Final support month
OpenWrt 25.12.5 Current stable; no 25.12.6 firmware release is listed Current stable
Package feed The August 31 change is a package-directory refresh, not target firmware Do not misreport
Device exceptions Clean upgrades, interface or layout changes, and special installers require model checks Must confirm

The August 31 packages refresh is not a 25.12.6 release; the exact device and migration notes still determine the upgrade path.

QUICK ANSWER

Confirm release state, then run a device-level upgrade preflight

Treat September 2026 as a migration deadline: 24.10 is not already unsupported on September 1, but security updates are planned to stop after the month.
The current firmware releases remain 24.10.8 and 25.12.5; an updated package feed is not a new firmware release.
Confirm the exact model, hardware revision, target, profile, and 25.12 support before downloading firmware.
Save the configuration backup off the router and record packages, feeds, VPN, firewall, VLAN, and custom network settings.
Use a complete official firmware upgrade through sysupgrade, Attended Sysupgrade, or owut—not a blanket apk upgrade.
If device-level evidence is incomplete, pause instead of forcing an image or assuming configuration can be preserved.

EVIDENCE-BACKED UPGRADE PREFLIGHT

Decide from version, device, configuration, and recovery evidence

Pause when device evidence is incomplete. EOL timing, package-feed activity, or “most devices” support is not enough by itself.

Step 1
Release state

Confirm the installed version, stable, and old-stable releases; do not infer firmware versions from package-feed timestamps.
Step 2
Device evidence

Verify the exact model, revision, target, profile, and any clean-upgrade, interface, or special-installer exception.
Step 3
Configuration plan

Save an offline backup and record packages, feeds, VPN, firewall, and network settings; plan a rebuild when required.
Step 4
Preflight result

Migrate only with complete evidence; otherwise rebuild config, prepare a device-specific Recovery Pack, or postpone.

PLAIN-LANGUAGE TERMS

Terms you will see during recovery

Sysupgrade

OpenWrt’s complete firmware upgrade mechanism for a supported device and image.

Attended Sysupgrade

A Web workflow that requests a complete image while accounting for the selected package set.

owut

OpenWrt’s command-line upgrade tool for checking and requesting a complete image.

Clean upgrade

Installing without old configuration when a device or migration path requires a fresh setup.

Recovery Pack

A device-specific preflight record containing the official image reference, checksum, recovery IP, filename, and documented recovery method. It is not a stored or repackaged firmware file.

ACTUAL STATE AND DEVICE RISK

Turn the EOL event into a verifiable device migration decision

September is the final planned support month—not an instant cutoff

OpenWrt projects 24.10 end of life for September 2026 and says security updates will stop after the month. Plan the migration while the router is healthy, but do not translate the date into permission to flash every device immediately.

Read firmware state separately from package-feed activity

As verified September 1, the release pages still identify 24.10.8 as old-stable and 25.12.5 as stable. The 25.12.5 packages directory changed on August 31 while target firmware remained dated June 30; that does not create a 25.12.6 firmware release.

Confirm that 25.12 supports the exact device

Most 24.10-supported devices can move to 25.12, but model-specific exceptions remain. Verify the model, hardware revision, target, profile, image type, and any clean-upgrade, special-installer, or partition-transition requirement.

Back up more than the configuration archive

Download the official configuration backup to another device. Also record important packages, custom feeds, VPN and firewall rules, VLANs, interface names, and any manual startup or network changes needed for a clean rebuild.

Use firmware upgrade tools, not apk upgrade

A package-manager update does not replace the kernel, base image, and target-specific firmware as one tested unit. Use the official sysupgrade path, Attended Sysupgrade, Firmware Selector, or owut and review every package and validation warning.

Use the preflight result instead of a universal upgrade answer

Proceed only when the official device path is clear. Rebuild configuration when required, prepare a device-specific recovery record when the flash carries extra risk, and pause when target, profile, migration, or recovery evidence is missing. TFTP is only one possible recovery method.

FINAL CHECK

Four outcomes from Upgrade Preflight

Normal migration: official device path, target/profile, and configuration conditions are clear
Rebuild configuration: device instructions require a clean upgrade or post-migration setup
Prepare a Recovery Pack: record official image, checksum, IP, filename, and exact recovery method
Postpone: device support, migration exception, or recovery evidence remains unclear

MACOS RECOVERY AFTER FAILURE

Record the recovery method before upgrading; do not swap firmware blindly after failure

If the exact device really uses TFTP recovery, Router Recovery helps check the temporary IP, Ethernet, firmware file, and local TFTP waiting state.

Prepare an OpenWrt Recovery Check Review image-check boundaries

FAQ

OpenWrt 24.10 to 25.12 questions

Is OpenWrt 24.10 already unsupported on September 1, 2026?

No. OpenWrt describes September 2026 as the projected end-of-life month and says security updates will stop after September. Treat the month as a planning deadline rather than an instant cutoff.

Should I move from OpenWrt 24.10 to 25.12?

OpenWrt recommends migration, but the answer for a specific router depends on exact 25.12 support, target and profile continuity, migration exceptions, and whether configuration may be preserved.

Did the August 31 package-feed update release OpenWrt 25.12.6?

No. The official release state still shows 25.12.5. Package feeds can be refreshed without publishing new target firmware.

Should I use apk upgrade to move the whole router to 25.12?

No. Use a complete firmware upgrade through supported OpenWrt tools. apk add for an individual package is a different operation from replacing the firmware release.

Can I preserve configuration during the upgrade?

Often yes, but not universally. The exact device and release notes can require a clean upgrade, interface changes, or a special migration procedure.

Can Router Recovery perform the OpenWrt upgrade?

No. Use OpenWrt’s official upgrade tools. Router Recovery helps prepare the Mac-side TFTP recovery environment only if the exact device needs it after a failed flash.

NEXT STEP