NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Feb 27, 2016R7000 BETA 1.0.6.40 ..........SOS..........Different version #
I was somewhat excited to hear that a Beta was being passed around today. 1.0.6.40 So I downloaded and installed it correctly. I entered my settings while off line using a wired connection. The 1st ...
- Retired_MemberFeb 27, 2016
With last Pulled version I had successfully disabled ARLO via arlo setup. Several days later I turn 2.4 off from the advanced wireless settings menu and arlo popped up.
This time with the latest FW I again successfully turned it off from the arlo setup page and when pushing the front button the main SSID's turned off and arlo popped up.
I have no interest in testing Jack Squat any further. If and when I need to use the r7000 I'll once again go thru the whole fricken default, reset , powercyle and while facing fricken mecca install 1.0.4.30 again.
mondenath
Feb 28, 2016Prodigy
you are doing a mistake Why are you using the physical button on the router rather the gui based setting. You already know beta firmware could trigger anything since its not being final version. May be the physicall button is triggering all the wifi ssid.
More over the ssid for arlo in advanced wifi should have option though the arlo seperate settings.
But for my setup the 1.6.40 is working fine with no arlo on . Its working stable for past 12 hrs and no hang or net issues as well. Everything is working well with over 9+ devices streaming from net and locally via connected USB with 2 more routers connected via WIFI-bridge and 2 readyshare is working in conjuntion.
Hope if you re-do without touching the wifi button and configure everything from router gui things should go smooth for you.
Retired_Member
Feb 28, 2016Your missing the point.
I'm not testing connections or any other options. I don't care. My point is ARLO shouldn't be on UNLESS user selects it to be on. That's it nothing else.
Glad your happy with.
- sir_bazzFeb 28, 2016Apprentice
@searay wrote:My point is ARLO shouldn't be on UNLESS user selects it to be on. That's it nothing else.
I'd agree with that......would keep it consistent with other optional elements within the firmware.
And while I don't know the reason why they went down that path, (I don't own any Arlo products), it's also not a bug in the formware.
Still just under 2 days of uptime but looks the most promising so far.
All good with the config I run and this was coming from 1.0.3.61_20140605_QA and without any resets or re-entering configs after the update. Even the port forwarding kept working without having to remove/re-enter.