I've been waiting for the WRT3200ACM to reach a more stable point in recent builds, so I've been hanging out on 19.07.8 for a while. However, 19.07 is getting dated, and I want to try getting on a recent version. My only requirement is that I want to be able to fallback to my current 19.07.8 configuration if the latest snapshot is unstable. I fully expect to redo my configuration on the new release.
My question is, is it safe to install the latest snapshot from 19.07.8? Any OpenWRT 22.03.x builds say they cannot be upgraded from 19.07, but I don't know if this applies here since the WRT3200ACM has two partitions and its writing to the other one.
If this isn't a safe upgrade, then I need to upgrade from 19.07 -> 22.02 -> snapshot. In this case, I need to ensure that when I upgrade twice, that I preserve 19.07. This forum post describes upgrading with the same partition - so my plan for this scenario is as follows:
Upgrade from 19.07 -> 22.02
On reboot, I should be on partition with 22.02, and 19.07 preserved
switch ubootenv set boot_part to the opposite given value
Upgrade from 22.02 -> snapshot
I should now be on the latest snapshot, with 19.07 still preserved
If I need to do this route, does it sound like a good plan?
Your idea will not have the desired outcome. Upgrade is a round-robin, it goes to the other partition, whatever other is when you pull the trigger, setting env vars as part of the process.
It is fine to just go from 19.x to master, you will get the warning as there is the change to DSA, just do not keep your config,
there is still pending issue, may or not may not be an issue to your use-case.
may be of some use:
bootTaOther
#!/bin/sh
#hacked from /lib/upgrade/linksys.sh
cur_boot_part=`/usr/sbin/fw_printenv -n boot_part`
target_firmware=""
if [ "$cur_boot_part" = "1" ]
then
target_firmware="kernel2"
fw_setenv boot_part 2
fw_setenv bootcmd "run altnandboot"
elif [ "$cur_boot_part" = "2" ]
then
target_firmware="kernel1"
fw_setenv boot_part 1
fw_setenv bootcmd "run nandboot"
fi
# re-enable recovery so we get back if the new firmware is broken
fw_setenv auto_recovery yes
echo "$target_firmware"
reboot
I don't currently use VLAN for my simple network, so I'm not sure that will pose an issue. My current setup uses the following major components: Unbound + ohdcpd, adblock, wireguard, ipban, SQM.
In short, the snapshot release (what I linked previously) doesn't work when I try to upgrade. I tried 21.02.4 and it worked easily. For both upgrades, I downloaded the file directly on the router and ran sysupgrade as follows:
sysupgrade -v -n --force /tmp/[...].bin
Maybe there is something I'm not doing correctly, but I can't seem to upgrade the latest snapshot from 19.07.
Again, might be related to the release notes of the latest version:
:!: Sysupgrade from 19.07 to 22.03 is not supported.
Yes everything is working as expected now.