Published Nov 21, 2026, 2:30 PM EST Shekhar Vaidya is a veteran technology journalist and computer science engineer. He is the founder of TechLatest, where he has spent years providing technical analysis on hardware and Windows ecosystems. Now a Computing Writer at XDA, Shekhar leverages his deep background in NAS, storage solutions, and PC internals to help readers master their tech. Routers are networking devices we use every day, but we rarely look at the admin panel after the initial configuration. I use an Archer C6 as my main Wi-Fi access point at home. I was shocked to find out about TP-Link’s last update for this router. The build date was July 16, 2025, and it was released on December 9, 2025. Almost a year without any official updates for my model. Most users underestimate routers. It might not be the most interesting gear in your networking squad, but it is the only device responsible for broadcasting Wi-Fi for every device in our houses. Given my background, I flashed OpenWrt, a custom firmware, months ago out of curiosity. When I switched from the official TP-Link firmware, I wasn't worried about security updates, but later on, I learned their importance and understood why that curiosity-driven switch was worth it. TP-Link kept patching every C6 but mine A year of nothing, by the dates I got my first router, the Archer C6, on April 1, 2022, and it's still working the same way it was. And I am sure it will work the same way for the next few years. I am sure because of the custom firmware community, not the official support. Why not the official support? I already told you about the update cycle. Even I was surprised to see the last update date. Given that TP-Link sells more routers than most, and the Archer C6 (or A6) is among its best-selling budget routers, I was curious why there has been no update for a year. For context, my specific model is Archer C6 V3, and it has several siblings like V6 and V2. While I was looking into it further, I discovered that I was the only one (V3) stuck on a July 2025 build, while the siblings kept getting updates. For instance, the V2 recently got an update, the 1.2.1 Build 260902, built September 2, 2026, and its latest security advisory was updated on October 21, 2026. The scenario is similar for V6 as well; it was last updated on September 10, 2026. Then I assumed there might not be any major security issues found for routers in the last year, but I was wrong there too. I found botnets like SocksEscort and AryStinger, and one (CVE-2023-33538) was even targeted at TP-Link’s EoL routers. There were no disclosed CVEs specific to my model, but it all ends with a big “what if.” The risk is that if one appears, it won't get fixed. While doing all the research, I was a little relieved too because I already switched from the official TP-Link firmware to OpenWrt. But once I landed on its web admin panel, the story was something else. I left TP-Link and fell behind anyway My OpenWrt build went end-of-life too After the research, I casually opened the OpenWrt web admin panel. The first thing I noticed was the firmware version, because once logged in, the overview page is the default. The firmware version was OpenWrt 24.10.5. I assumed it was the latest version and decided to search for this version and read the release notes’ security updates. Well, it was a bit of a bummer to criticize TP-Link for not pushing updates for over a year and then me finding out my own flashed version was almost a year old. The OpenWrt 24.10.5 release page mentioned December 19, 2025, as the release date, and the 24.10 series had already reached end-of-life in September 2026. Then I checked whether this was the latest release or if I was just behind, and found out that I was the one who fell behind on updates. There was a new major release, 25.12, and even the 24.10 series got a few security patches, like 24.10.7 in May and 24.10.8 in July. After that, I dug a little deeper into my installation. I flashed OpenWrt on my router last year around Christmas, configured it, and forgot about it once it was up and running. And since there was no way to check for firmware updates from inside LuCI (web UI) without the attended-sysupgrade package installed, I didn’t think of updating it. Then I checked the latest version available for my model, and it was 25.12.6. I downloaded it and flashed it immediately. The flash process was easy, but the result wasn’t straightforward. The fix arrived, and my packages left I won’t bore you with each and every step to flash a new firmware or update it, but while downloading the firmware, check which image you are downloading; there are usually three: SYSUPGRADE, FACTORY, and KERNEL. SYSUPGRADE is meant for updating, and FACTORY is for new installations. I am telling you this because I almost flashed the wrong one. Now, coming back to the new firmware. The process was seamless; after the flash, it was auto-loaded to the login screen. The best part was hitting the login button. After successful authentication, the first pop-up was the fix for the issue that let me fall behind on updates. It was a pop-up for enabling auto-check for firmware upgrades. It was the same attended-sysupgrade package I mentioned before, but this time it was installed by default. With it enabled, the system checks for upgrades each time I load the overview page. If it had been installed with the initial 24.10 build, I would have noticed two 24.10.X updates that had already shipped by the time I logged in to set up SQM and banIP in August. That being sorted, I checked all the settings and packages I had before. Most of them were intact, except a few. When I opened the Interfaces, wg0, which was previously the WireGuard VPN tunnel, now showed 'Not present' with the ‘Unsupported protocol type’ error. When I checked the software page, the WireGuard package was not even there. Then I dug further and found out that a few of my installed packages’ pages were also missing, such as banIP, nlbwmon, and SQM. It was a side effect of 25.12’s migration from the opkg to the apk system. The stock image only carried the basics, meaning the configs stayed, but the packages and the whole Services menu were gone. Well, those are one-time things; once I install WG and reconfigure things my way, it will be a reliable device again. Still worth it, with one condition Zooming out from the specifics, yes, OpenWrt is firmware that will help my 4-year-old router live longer as long as I open the admin panel once in a while to check for new firmware updates. The flashing process is easy, and it opens up new possibilities for old hardware. It even helped me overcome my ISP’s limitations. If you are in a similar situation, give OpenWrt a try; it might help revive your old router. OpenWrt OpenWrt, from open wireless router, is an open-source project primarily used to route network traffic for embedded operating systems based on Linux.
I thought OpenWrt was keeping my router safe, but it was a year out of date
Full Article
Original Source
Read the full article at Xda-developers →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.