{"id":1900,"date":"2021-10-10T11:38:53","date_gmt":"2021-10-10T15:38:53","guid":{"rendered":"https:\/\/lowtek.ca\/roo\/?p=1900"},"modified":"2021-10-10T11:38:53","modified_gmt":"2021-10-10T15:38:53","slug":"openwrt-19-07-to-21-02-0-upgrade","status":"publish","type":"post","link":"https:\/\/lowtek.ca\/roo\/2021\/openwrt-19-07-to-21-02-0-upgrade\/","title":{"rendered":"OpenWRT 19.07 to 21.02.0 upgrade"},"content":{"rendered":"

\"\"<\/p>\n

I’ve long been a fan of open firmware for my home routers. Way back I started with DD-WRT<\/a>, but more recently I’ve moved to OpenWRT<\/a> paired with TP-Link Archer C7<\/a> hardware. I actually have two, one as my main gateway and a second configured as a dumb AP <\/a>(access point). Running two WiFi access points means I get great coverage from the basement, to the second floor.<\/p>\n

While I have two, they are not quite identical. One is a v5, and the other is a v2. Still, for hardware you can pick up for under $100<\/a> it fits into my sweet spot for hardware. I picked up both of mine used, for less than half the price of new hardware. The other benefit to having two which run the same software stack (OpenWRT 19.07), means I can swap hardware for the main gateway if I have a compatibility problem.<\/p>\n

Recently the latest version (21.02) has been declared stable. It’s well past time to upgrade<\/a>. With the hardware I have, OpenWRT has recently done a transition from ar71xx<\/a> to ath79<\/a>. Thankfully In my setup with 19.07 I’d already moved to ath79.<\/p>\n

You can check the TARGET<\/code> that you are running by ssh’ing into the router and looking at the \/etc\/openwrt-release<\/code> file<\/p>\n

# cat \/etc\/openwrt_release  | grep TARGET\r\nDISTRIB_TARGET='ath79\/generic'<\/pre>\n
It is a good idea to start with the release notes<\/a>. The upgrade process is 3 parts.<\/p>\n
    \n
  1. Prepare<\/li>\n
  2. Upgrade<\/li>\n
  3. Post Install Configuration, Setup or Restore<\/li>\n<\/ol>\n
    \n
    <\/div>\n<\/div>\n
    We’ve already started the Prepare<\/strong> step since we have looked at the release notes and made sure we have the ath79 version running. Since we’re already on ath79 we can use the normal sysupgrade process. OpenWRT is also moving to DSA Networking<\/a>, but the hardware I’m using hasn’t switched over yet – the upgrade process will detect this and refuse to upgrade if you have a problem.<\/p>\n
    I’ve got a full rsync backup of my router configuration, so if something goes really wrong I at least have the files.<\/p>\n
    Next I need to figure out which packages I have installed on the router(s). This script<\/a> seems to work well, I’ll duplicate the script here.<\/p>\n
    cat << \"EOF\" > \/tmp\/listuserpackages.awk\r\n#!\/usr\/bin\/awk -f\r\nBEGIN {\r\n    ARGV[ARGC++] = \"\/usr\/lib\/opkg\/status\"\r\n    cmd=\"opkg info busybox | grep '^Installed-Time: '\"\r\n    cmd | getline FLASH_TIME\r\n    close(cmd)\r\n    FLASH_TIME=substr(FLASH_TIME,17)\r\n}\r\n\/^Package:\/{PKG= $2}\r\n\/^Installed-Time:\/{\r\n    INSTALLED_TIME= $2\r\n    # Find all packages installed after FLASH_TIME\r\n    if ( INSTALLED_TIME > FLASH_TIME ) {\r\n        cmd=\"opkg whatdepends \" PKG \" | wc -l\"\r\n        cmd | getline WHATDEPENDS\r\n        close(cmd)\r\n        # If nothing depends on the package, it is installed by user\r\n        if ( WHATDEPENDS == 3 ) print PKG\r\n    }\r\n}\r\nEOF\r\n \r\n# Run the script\r\nchmod +x \/tmp\/listuserpackages.awk\r\n\/tmp\/listuserpackages.awk<\/pre>\n
    This will dump out the list of packages that you have installed beyond the stock configuration. I’ve got rsync<\/code> installed (of course) along with the prometheus<\/code> packages. The upgrade will not automatically install these packages, so having the list of them helps us get back to the configuration we are used to.<\/p>\n
    We should now be ready to Upgrade<\/strong>. I found the easiest way to get the right sysupgrade package was using the Firmware Selector<\/a> web tool. Since I have slightly different versions, I needed to make two downloads.<\/p>\n
    It is always a good idea to check the hash (sha256sum) of the files you download to make sure you have a good download. I’ve been burned only a handful of times by this, but once should be enough to teach you the lesson.<\/p>\n
    Using the Web UI to upgrade can be found in the menu system: LuCI \u2192 System \u2192 Backup \/ Flash Firmware \u2192 Actions: Flash new firmware image<\/strong>.<\/p>\n
    Time for a deep breath, and double check we have a backup. Time to flash, also double checking we push the right version to the right device.<\/p>\n
    After flashing the 1st device, I noted two things. The “flashing” screen seemed to get stuck – well past when the device has refreshed. Using a second browser window, I think I figured out why things got stuck. The LuCI web UI<\/a> now redirects you to https:\/\/ with a self signed certificate. I think the browser on the flash screen got stuck because of the change in protocol (and the bad cert).<\/p>\n
    It’s good that the web UI is now hosted using https because now when you log in, you’re not sending your passwords in the clear. Sure it’s your own network, but I think I’d rather have to deal with clicking through the advanced screens to tell my browser to accept the self signed certificate than not have a secure connection.<\/p>\n
    For the Post Install Configuration, Setup or Restore <\/strong>step\u00a0it’s a matter of going through the packages I’d identified above and re-installing them. As a second check, I also re-installed an re-ran the listuserpackages.awk script and got the same list back once I’d installed all the packages.<\/p>\n
    I can also verify that all of the configuration files made it by testing the functions these additional packages had. All was good, at least with my dumb AP.<\/p>\n
    My main gateway router was a bit scarier – it’s got a few more packages installed than the dumb AP and when I update it, I take an internet outage. Also, I ran into trouble trying to update some of the modules:<\/p>\n