NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 New Firmware 1.0.6.28 released
New Features:
- Supports Arlo camera. Set up the R7000 as an Arlo base station and connect an Arlo camera to the R7000 without needing an extra base station..
Bug Fixes:
- Fixes the issue in which port 1237 cannot be used in port forwarding.
- Fixes the issue in which the Kwilt binary cannot be downloaded in some cases.
- Fixes the issue in which MTU is not restored when IPv6 is disabled.
If you are going backwards in release number you might still have them (that is from one of the older recalled beta's). However there is NO guarantee they will work. In cases like that you have to RESET the router and then re-apply manually your setting for proper operation.
If you are moving up from and older official release, like V1.0.4 or older you don't need to reset the router but it is advised. In this case I'd give it a try, have any problems, reset and re-enter is the first thing to try. DO NOT load saved settings from any other version into a new one. That seems to be asking for trouble these days.
320 Replies
Replies have been turned off for this discussion
- Yes, 10.11.4. TBH, I've run OS X betas for a while and the risk is negligible as long as I have a prior working backup. Usually, any antivirus issues are related to changes in how System Integrity Protection works. I currently use Sophos antivirus. That, however, doesn't really have any bearing on this thread as the issues I'm facing are present via the Arlo iOS app and the MyArlo site in OS X and Windows 10-based browsers. While I appreciate the input, I'd also like this thread to stay on topic.
Hi Vash,
Please check your inbox.
Considering your are using a what betera 2 of 10.11.4 with windows 10 there could be issues that effect you. Runnig a partion with 10.11.3 would be helpful trouble shooting wise I would have thought, that was why I mentioned it. Also as you know never run a beta on a main machine, even Apple say that. So the interface with 10.11.4 and the My Arlo site using Windows 10 is relavant I would have thought as 10.11.4 is the base that all this happens on.
Upgraded to this release and then the 2.4GHz SSID would always fail to authenticate on multiple devices from PC to iPad to Mac to Amazon Fire. Investigated the issue using WiFi analyser on Android phone and noted that the 2.4GHz non-Guest non-Arlo SSID existed twice with two different MAC addresses, one marked Netgear and the other marked Local Admin (which I believe indicates the vendor mac identifier). Trying to connect always resulted in an authentication problem reported on the Android phone. I reverted to 1.0.5 and immediately everything was fine and the strange duplicate SSID was no longer present.
Seems clear to me that this firmware has a major bug with SSID handling likely generated by the addition of the ARLO capability. Seems I need to wait for the next release after this.
Reset to factory defaults as has been mentioned in many places on the firmware 1.0.6.28 related threads.
If it still has problems, then abandon that version and downgrade.
I just checked my network with WiFi Analyzer on Android and I only see one mac address each for 5G, 2.4G and 2.4G Guest. But, my phone frequently looses internet access on either of my two non-guest networks. If I switch over to the other one, I'm back in business. Annoying but not a show stopper. Most of my stuff is on a wired network. I also saw the problem with my previous FW, which I don't recall. I wonder if there is a partern here. Also, I have had Arlo disabled since the first post in this thread.
It Seems the gui is slow that 5.4 series firmware. Its more sluggish nowadays than centria.
Hope it will get fixed next update.
- None of the devlopers are responding here.... Fail number 2
Hi Shadedred,
The 5Ghz issue that you have mentioned has been forwarded already to engineers. I will be providing feedback for any updates.
My Issues with 1.0.6.28_1.1.83
*Smart Connect does not work with secure applications such as Good email client
*Smart Connect roaming from one band to the other results in disconnect requiring manual WiFi release/reconnect.
smart connect is really not worth using tbh. Just use two different SSID's and pick the one that gives you what you need eithe on 5Ghz or 2.4 Ghz
Immediately following this update I lost my two Samsung Wifi Camera connections and all 5 Nest Protect Smoke Detectors. I was able to re-open all the port triggers that got wiped by the update but no luck getting the two cameas back on-line. Other 2.4 GHz connections are working fine but not the Cameras - Yes using same SSID and PW, etc. I finally regressed back to the prior release, restored my configuration file and viloa! everything works again. Yes, I tried disabling the Ario support but that made no impact in this case. Something very messed up with this release.
And the problem reports keep rolling in...
Come on Netgear, pull this release already.
- Yikes this is bad firmware. All transmission just randomly stops and my Nest thermostat had an error unable to connect and no IP.
- None of the developers are responding.. Very bad support. And this is my last time i buy a Netgear router.
I didn't have any issues too till first beta. Everything works well.
Hi,
Really annoyed that this driver isn't up, just bought a Arlo camera and now nothing to connect it with. Can anyone email me the firmware. I dont use all the fancy settings on my router so dont think port forwarding issues will bug me. email steveo_chi@hotmail.com
Thanks
Steve
- For anyone else that purchased a camera expecting to be able to use Arlo without a standalone Arlo hub, I suggest you contact Netgear Support and reference that you're having issues with Arlo when using the R7000 as a base station pertaining to the now officially unavailable firmware. You will be taken care of particularly if you now have standalone cameras and no available standalone base station. My current understanding is that they are currently abandoning Arlo functionality in the R7000. They likely didn't do thorough enough testing to try and represent the variety of possible network configurations and clients used from customer to customer. The Arlo functionality appears to cause far more issues and instability than anything else. Plus, I for one am tired of resetting and reconfiguring my router to troubleshoot non-core router functionality. I am, however, happy with the resolution offered by Netgear Support.
- Where did you hear they are abandoning Arlo support? I know they pulled the latest FW version that had it, but only because it caused so many problems. What I do object to is that the Arlo feature was turned on by default, although this itself probably isn't the root of the problems people encountered. I imagine that a very small percentage of the users actually are interested in Arlo support. I think it should have been off by default, but plainly visible in the setup so that anyone who does want that feature can easily turn it on.
- Totally agree, Arlo support should be turned OFF by default. You don't see Access Control, VPN, Parental Controls, etc., ON by default because vanilla configurations should be as simple and barebones as possible. That was a bad decision by Netgear, and probably a decision driven by marketing. That being said, I'm still interested in Arlo support for the R7000. Heck, before they added support in this firmware release, I didn't even know what Arlo was and never considered using Arlo cameras. But now I plan on picking up an Arlo Wire-Free camera b/c it's so convenient; so hopefully they don't remove support. I noticed they've removed the Arlo FAQs for the R7000. I get "access denied" on the Netgear site when trying to access the webpage. I'm definitely bummed about this firmware being so buggy, but I can live with the current workaround. Hopefully in the next week or two they'll have this straightened out and release a stable firmware. Regardless, I know I'll have to do a factory reset and re-apply all my settings just to make sure there's no weird junk left over from this buggy release. *fingers-crossed* they don't take away Arlo support.
