It would be nice to have a sort of choice for automatic updates. (As I have in my Nextcloud installation. Also not good to skip updates).
Eventually, sometimes in the future, I am sure this upgrade process will be more smooth.
I dont think it is expected that all users of openwrt have to be advanced enough to take care a manual upgrade and its packages as well.
In several cases, one might install the router at mom place or sister or friends for a better performance and security.
That does not means is constantly supported.
And I know that can be argued too.
But real life teach more than theoretical procedures.

Back to my situation, I am not sure how I can move on on my main router. I cant allow down time in my network (that is also my home and serves my family internet and TV).
I guess I have to find a second router to play with and see if I can rebuild everything and put that in service...
Not too happy... but I have no choices now
Thanks for the knowledge exchange.

Yes, it would. Someone would need to design such a feature, work through the complexities of updating the hundreds (thousands?) of add-on packages that are possible when using OpenWrt, get buy-in from all of the developers who would be impacted by additional work (to log pertinent changes in a machine-decipherable form), test, deploy and maintain it. Sounds like a full time job for maybe two people for the first year, then tailing off to a half-time job after it's all built out, tested and running smoothly.

Or we could just do what TP-Link and Zyxel and Netgear and everyone else does and just never publish updates...

Our current situation is between those two extremes, it's left up to the user to handle the complexities (or simplicities!) of their specific installation, as everyone has different needs and desires.

It might be time to consider your backup plan. What would you do if a capacitor popped inside and killed your current device?

My solution is to have a backup device on hand, I have another functionally-equivalent x86 router on my desk right here. It is usually running experimental configurations and SNAPSHOT builds so I know it's working, but it is ready to be put into service at a moments notice.

And since you mention remote installs... I also have installed RT3200s with three family members around the world, so I keep a spare one on hand here, ready to configure and ship out if any of theirs have issues. The spare RT3200 also acts as a backup WAP, but I've got a few older wireless all-in-ones that I could also swap in, if needed (and in a pinch, they could become the main router, too).

We will make the best out of it.
Yes, we should have a backup plan. Sometimes One rely on hardware more than software and is not necessarily a good thing.
I am no coder and I have (as you pointed out) no idea how complicated is to create a procedure such the one I suggested. Sometimes ago, I was pointed out to the attendedsysupgrade that looks pretty much similar to what I suggested.
I though my suggestion was just an improvement of it.

Mine was a simple suggestion.
I believe that software improves with user experience feedback.
Does not mean everything will be implemented. I am well aware of this! But mention it is probably important.

I think in time, everything will be made easier. When I look at Openwrt how it was years ago and how improved is now, I can only imagine how will be in a few years.

My conclusion is that Openwrt remain a great software and I will keep using it and deploy it to friends and families.
Not sure I will give a second device as a backup to each of them. (the isp router set aside is always a temporarily backup I guess)

Thanks for all the help and conversation here.Sounds like you are well involved in the openwrt project. Thank you for all your work.


This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.