NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware Downloads
FYI here's a little script that downloads all available firmware versions starting with v6.0.0. It'll be good to keep them on hand for the day that they go away online. Unfortunately, however, so...
The notes were only for those who are doing an offline local update
Yes, that's what I was referring to.
They could have built in the enforcement logic. Or even made them cumulative.
But oh well... here we are.
They could have built in the enforcement logic. Or even made them cumulative.
Maybe.
No idea why this matters to you now, since you aren't running 10 year old firmware, and shouldn't be trying to downgrade to something that old.
At this point it doesn't affect many people (only Arm ReadyNAS users who never updated their firmware or perhaps purchased used). And it is in the release notes and the KB articles.
Maybe
Absolutely.
It's a mistake to tell a programmer that something can't be done 😉
No idea why this matters to you now, since you aren't running 10 year old firmware, and shouldn't be trying to downgrade to something that old
From elsewhere in this thread:
The concern arose when I went shopping on eBay for a used ReadyNAS. It occurred to me that, should I purchase one, its patch level upon arrival would be unknown.
Also, having the collection on hand will be useful in the event of a necessary system reset
p.s. Does a reset walk back the version number? I don't recall offhand.
Does a reset walk back the version number? I don't recall offhand
No, it does not. Once an update is completed, there is no remnant of the previous version from which it could be restored.
No, it does not
Ah. That's good to know.
That relieves half of the concern.
Does a reset walk back the version number?
No it doesn't. When you install firmware, the image file is put into the flash. So a reset preserves the firmware version.
The concern arose when I went shopping on eBay for a used ReadyNAS. It occurred to me that, should I purchase one, its patch level upon arrival would be unknown.
Also, having the collection on hand will be useful in the event of a necessary system resetI already addressed that. In the case of a very old arm ReadyNAS, you'd want 6.2.5, 6.3.5, and 6.5.2. Though you can do without 6.3.5, since it is possible to downgrade 6.3.4 and 6.3.3 firmware to 6.2.5.
For all ReadyNAS, you'd then want 6.10.10 (though some might prefer 6.10.9).
No need for any other firmware.
Though if you did get a NAS with very old firmware, I recommend doing a factory reset after it was brought up to date. There was at least one case where Netgear said that would improve performance.
Absolutely.
It's a mistake to tell a programmer that something can't be done 😉I am a programmer... I didn't say it couldn't have been done. I said "maybe". I expect they could have put a check in the deb file to prevent the install. Consolidating the needed updates into all future firmware might not have been practical.
There are some physical constraints on the size of the deb file (since it does need to be installed into the flash), and they also would have needed to deal with both USB recovery and the normal install. I think there were also some post-install scripts that needed to be run after updating the kernel in these older releases.
There are a lot of other things I wish Netgear had done along the way that I think would have been more valuable. Keeping up with new debian releases along the way is the big one. But no real point in coulda, shoulda now.
No it doesn't
Ah. That's good to know.
That relieves half of the concern.
In the case of a very old arm ReadyNAS, you'd want 6.2.5, 6.3.5, and 6.5.2
I see that, not having looked at the 6.10.10 release notes until just now. I must've glossed over your explanation. That relieves half of the remaining half of the concern.
According to the releases the script found, the final x86_64 release covers models up to RN4220. Didn't you say earlier that RN product line numbers went higher than that, even into the 700s? It didn't find anything in a 700 branch; the aforementioned release was in the 300 branch (of the URLs).
That's why I'm interested in parsing the XML and scraping the KB articles for download links; the script's current sequential count approach is clearly blasting past a bunch of releases that are out there somewhere.
I am a programmer
Pleased t' meetcha 😊
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
