NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
perfarny
Mar 16, 2020Guide
FYI: Firmware update 2.5.1.8 causes DNS timeouts only fixed by reboot on my RBR50 and RBS50's
Hi All, Mostly an FYI as I've downgraded back to 2.3.5.30 and all is well again. I have one RBR50 and three RBS50's that have been working flawlessly for pretty much as long as I can remember be...
Retired_Member
Mar 16, 2020
OrbiPhilip wrote:This explains the other comment I replied to. I did not manually upgrade, that I am aware of, and I am on 2.1.5.8
Retired_Member wrote:The part I missed is how you came upon 2.5.1.8.?
The recommendation is to stay away from manual updates.
could be...I believe i saw the same thing with....FM ....2.3.5.30
when it was first available it was bad....then after a few months, NG started pushing it out auto. I've been on it since Oct19.
FYI...to me manual means you clicked something to start the download. auto means you wake up and there it is.
OrbiPhilip
Mar 16, 2020Luminary
Retired_Member wrote:when it was first available it was bad....then after a few months, NG started pushing it out auto.
Are you saying that we should not only be looking at major/minor versions, but also build numbers? Is Netgear releasing those?
IMHO, if the version of 2.3.5.30 released on day 1 (manual) and the version of 2.3.5.30 released on day XX (automatic) are not the same, then they need to be appending build numbers to the version. Or at the very least, alpha, beta, GA, etc.
- OrbiPhilipMar 17, 2020Luminary
Knock on wood, zero timeouts since downgrade to v2.3.5.30 (~7.5hrs). Prior to that it was 5-10x per day.
- Retired_MemberMar 17, 2020
OrbiPhilip wrote:
Retired_Member wrote:when it was first available it was bad....then after a few months, NG started pushing it out auto.
Are you saying that we should not only be looking at major/minor versions, but also build numbers? Is Netgear releasing those?
IMHO, if the version of 2.3.5.30 released on day 1 (manual) and the version of 2.3.5.30 released on day XX (automatic) are not the same, then they need to be appending build numbers to the version. Or at the very least, alpha, beta, GA, etc.I'm saying do nothing.
NG will push critical updates when needed. IF your system is working OK, there is no need to update. Some feel the next update is needed or will boost performance. They have basically become BETA testers.
I understand how build numbers work. I can only share what I saw. A simple search here going back to last summer should reveal the problems with 2.3.5.30, which is the case in most FW manual updates. Remember, a few years ago, there was no choice, NG pushed everything. Now, they make a FW available and it's up to the user to decide if they want to 'try' it. If you like living on the edge, go for it.
- OrbiPhilipMar 18, 2020Luminary
Since downgrading from 2.5.1.8 only one DNS failure and that was at only one of my test sites, which seems to indicate a problem with that site.