NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 firmware version 1.0.5.64_1.1.88 released today
New Firmware Version 1.0.5.64_1.1.88 Release Notes 1. [New Feature] Supports Smart Connect. 2. [New Feature] Supports the Kwilt app, which can be used to view photos stored on the...
That IS the newest OFFICIAL Firmware release. The beta you referenced was pulled and newer ones with V1.0.5.60 and .62 were released WITHOUT Arlo support and provided for improve stability which is the reason OLD Beta's were recalled and deleted from distribution.
If you require Arlo support, call NG for firmware that supports it it seems.
Since when V1.0.6.26_1.1.83 was a beta driver? It was the official driver that NG released and that many people had problem with. It's working perfect on my rig.
It's really stupid... Even if the newer driver are a step backward in terms of options, they should have upgraded the versions as it's supposed to be... V1.0.7 something... And so on.
First time I hear and see a newer driver with an older version :O
I suspect the drop back was because Arlo support was REMOVED and they worked off the LAST beta without Arlo support. Reason given was 'stability'. Normally later versions do NOT drop functions but add them, and that is probably the reason why. Need Arlo Support, call them, they seem to have a beta now with it and that will probably be in the next firmware official release.
Welcome to the world of release branches.
Think of 1.0.6 as R2.0 in the picture, below, and 1.0.5 as R1.0. The code they put into 1.0.6 was so buggy (interpret this as unfixable in a reasonable amount of time) that they decided to pull the whole release. They actually pulled 1.0.5, too, but the situation must not have been so dire. They fixed the main issues on 1.0.5 and put out a new release, shown as R1.1. Eventually, they will release a patched version of 1.0.6. This would be R2.1, which isn't shown in the picture, but it would be a bubble to the right of R2.0.
Netgear certainly could have given each new release a higher number regardless of the code base it's based on (a lot of companies do work this way) but then the versions we see and what they see internally would have diverged. It's actually nice that Netgear didn't do this because it gives us some visibility into their release model.
