search

ExtremeFiretop / MerlinAutoUpdate-Router

Merlin(A)uto(U)pdate is a Merlin router script which allows you to remotely identify a stable firmware update for an ASUS Merlin router, and automatically download and update via an unattended method directly from the router.
https://www.snbforums.com/threads/merlinau-v1-2-7-the-ultimate-firmware-auto-updater-amtm-addon.91326/
GNU General Public License v3.0
21 stars 1 forks source link

Update Minimum Version to 3004.386.12.6 #305

Closed ExtremeFiretop closed 1 month ago

ExtremeFiretop commented 1 month ago

Update Minimum Version to 3004.386.12.6, our minimum version is currently 6 versions behind production or about 8 months behind production. Upping to 3 versions behind production. Last update in this regard was about 10 months ago.

Martinski4GitHub commented 1 month ago

Update Minimum Version to 3004.386.12.6, our minimum version is currently 6 versions behind production or about 8 months behind production. Upping to 3 versions behind production. Last update in this regard was about 10 months ago.

With this new "Minimum Version" supported, users that happen to be running F/W versions below 3004.386.12.6 but above 3004.386.11.0 would not be able to update to the latest 3004.386.14.0 version.

What are the concerns if these users were still allowed to do the F/W update via MerlinAU?

Is the main concern due to the big jump/gap between the F/W versions?

ExtremeFiretop commented 1 month ago

What are the concerns if these users were still allowed to do the F/W update via MerlinAU?

Is the main concern due to the big jump/gap between the F/W versions?

Exactly.

The intention of MerlinAU was always to keep a router up to date, not to be used to bring a router up to date over large version gaps. This was initially discussed in the forums when I was seeking feedback on the Addon.

I've always wanted to keep fairly close minimum version due to this.

The minimum version I see as dual purpose, it can be used when a specific firmware version is required for a successful update, but I don't believe that's happened recently, the second purpose is to be used to discourage users to install MerlinAU and use it to do one time flashes over many firmware versions.

Specific discussions comments were found here for reference:

Post in thread 'Seeking Feedback & Contributions: Merlin Auto Update Solutions' https://www.snbforums.com/threads/seeking-feedback-contributions-merlin-auto-update-solutions.87044/post-868605

Post in thread 'Seeking Feedback & Contributions: Merlin Auto Update Solutions' https://www.snbforums.com/threads/seeking-feedback-contributions-merlin-auto-update-solutions.87044/post-868608

Martinski4GitHub commented 1 month ago

What are the concerns if these users were still allowed to do the F/W update via MerlinAU? Is the main concern due to the big jump/gap between the F/W versions?

Exactly.

The intention of MerlinAU was always to keep a router up to date, not to be used to bring a router up to date over large version gaps. This was initially discussed in the forums when I was seeking feedback on the Addon.

I've always wanted to keep fairly close minimum version due to this.

The minimum version I see as dual purpose, it can be used when a specific firmware version is required for a successful update, but I don't believe that's happened recently, the second purpose is to be used to discourage users to install MerlinAU and use it to do one time flashes over many firmware versions.

Yeah, I see. If that's the case, then what about the 3004.388.xx version series? There's no "minimum version" check for it even though the first version came out on Dec-2022. IOW, a user running F/W version 3004.388.1.0 can still update to the latest 3004.388.8_2 (9 versions later, ~21 months apart). Should there be a minimum check for 3004.388.xx as well?

ExtremeFiretop commented 1 month ago

What are the concerns if these users were still allowed to do the F/W update via MerlinAU? Is the main concern due to the big jump/gap between the F/W versions?

Exactly. The intention of MerlinAU was always to keep a router up to date, not to be used to bring a router up to date over large version gaps. This was initially discussed in the forums when I was seeking feedback on the Addon. I've always wanted to keep fairly close minimum version due to this. The minimum version I see as dual purpose, it can be used when a specific firmware version is required for a successful update, but I don't believe that's happened recently, the second purpose is to be used to discourage users to install MerlinAU and use it to do one time flashes over many firmware versions.

Yeah, I see. If that's the case, then what about the 3004.388.xx version series? There's no "minimum version" check for it even though the first version came out on Dec-2022. IOW, a user running F/W version 3004.388.1.0 can still update to the latest 3004.388.8_2 (9 versions later, ~21 months apart). Should there be a minimum check for 3004.388.xx as well?

I never considered separating the branch versions with their own checks, but it's not a bad idea at all.

I just didn't want to bump to 388 when we still support two AC routers on 386 technically... But if we split it up then we could have a minimum for each... I like the idea the more I think about it.

Martinski4GitHub commented 1 month ago

What are the concerns if these users were still allowed to do the F/W update via MerlinAU? Is the main concern due to the big jump/gap between the F/W versions?

Exactly. The intention of MerlinAU was always to keep a router up to date, not to be used to bring a router up to date over large version gaps. This was initially discussed in the forums when I was seeking feedback on the Addon. I've always wanted to keep fairly close minimum version due to this. The minimum version I see as dual purpose, it can be used when a specific firmware version is required for a successful update, but I don't believe that's happened recently, the second purpose is to be used to discourage users to install MerlinAU and use it to do one time flashes over many firmware versions.

Yeah, I see. If that's the case, then what about the 3004.388.xx version series? There's no "minimum version" check for it even though the first version came out on Dec-2022. IOW, a user running F/W version 3004.388.1.0 can still update to the latest 3004.388.8_2 (9 versions later, ~21 months apart). Should there be a minimum check for 3004.388.xx as well?

I never considered separating the branch versions with their own checks, but it's not a bad idea at all.

I just didn't want to bump to 388 when we still support two AC routers on 386 technically... But if we split it up then we could have a minimum for each... I like the idea the more I think about it.

I think at some point, we'll have to "split" the current 3 branches (3004.386.x, 3004.388.x & 3006.102.x) in order to run a "minimum version" check for each, as appropriate for the router, but taking into account that for some routers it might be possible to go from one branch to the next (e.g. from 3004.388.x to 3006.102.x). Something to consider... :>)