NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Update V1.9.1.12 Netgear officially announcing 'Improvement in wireless connection Stability'
Just downloaded the latest release V1.9.1.12 and noticed in the official release notes from Netgear it states as fix 'Continious Improvement in wireless connection stability'..Dosent spefically makre...
We've been putting in significant work on these disconnect issues and wireless stability and every new release typically has improvements in it. The challenge is that there are literally thousands of devices running multiple versions of software that a router or WiFi System needs to work with, and occassionally interoperability issues arise as the two systems try to talk to each other. When that happens, rest assured that we're working very hard to stay on top of these issues and solve them.
When we come up with a proposed fix, we always want to test out our fixes in a real-world environment, before rolling it out for everyone and we use the beta program for that. At this stage, we think we have a solution for some of them but we want to test it out in a smaller environment. If you're interested in helping us, please feel free to contact Support.
Thanks,
Orbi Product Management
Netgear,
I understand Netgear, but your response only further validates my previous posts. Yes, there are FAR TOO MANY wireless client devices vastly ranging with capability, compatibility, and other artifacts which can cause instability. Many of the problems can be identified with the end-user’s ability to have advanced control of their Orbi, giving that user the ability to find the one, or more, features that do not work with their devices. Information about the connected devices such as RSSI, MCS Rates and other data points can quickly identify what I client device is doing. What you have caused with your LOCKED-DOWN Orbi configuration is HOURS, DAYS, WEEKS, MONTHS of end-users trying to identify their problems using far more complicated methods, NOT REQUIRED by other Wireless router/AP OEMs. All we asked for was transparency and access to advanced settings which I can think of NO REASON why you would restrict this. If your argument is “simplicity, ease of use, etc”….Well, I think I am not alone with saying, you failed! And what is sad, you didn’t need to fail. You only needed to open up the platform a little so users could quickly identify their problems.
I understand that most users are not technical enough to understand RSSI, MCS Rates, and other data points and what the mean. Which is why they depend on technical support and friends and family who are technical, for HELP. But, how could I help them with your locked-down platform? I am VERY technical. I understand WIFI in-depth. But any technical person needs information and ability to change behavior settings of WIFI.
Again, I thank you for your attempts to make something great, I thank you for showing your response and attempts to heal this platform. I thank you for working with me, and others, who are SERIOUS about helping you remediate the Orbi problems. The beta code you allowed me access to is doing MUCH better than 1.9.x.
But please listen to us. 20 years I have been doing this I.T. crap here in Silicon Valley for small, mid, enterprise and government customers. I live about 30 minutes from where you all sit in Santa Clara. We all know there is no one solution to help everyone. Every technology product usually requires a little customization to make it play friendly in various environments. I know you know this, so why is Orbi so locked down?
Just wanted to update as it's been a little while still on the current firmware.
Still working great. I have 30 devices on the wireless currently. And Samsung wireless soundbar 950 and oled tv and a 4K bluray are the latest editions.
Hey everybody,
just bought the system on Friday.
I did buy very early that day though, and read up on the problems everybody is having during that day.
Oh boy...
So i was thinking all day about returning it before even trying.
Still I went home and made the setup. Took me 15 Minutes, FW update was what took the longest.
This means i have been running V1.9.1.12 since the start of this little advanture.
I was actually quite impressed...
Currently I am running a Fritzbox as Modem.
Connected to that I have a new Asus RT-AC88U as my main Router an upper Floor / attic Wifi Host / Wired Land Controller.
I got the Orbi for downstairs / entrance / garage and garden Wifi because of the "stellar" reviews on snb forums and everywhere else.
Everything worked fine for I`d say about 24h.
this morning I came downstairs, Orbi Wifi was up, Sonos connected / Sonos controller on Ipad2 connected to the Orbi wifi and working but...
The Routernode was shining solid magenta.
Powercycling it a few times made it show up for a few minutes in my Asus overview of connected devices.
It got a dynamic IP, but the Router over the webGui was not accessible with its given IP. It was off its megenta-mode for a few minutes but went magenta again a few minutes later.
So after checking a few things i noticed my router (asus 88u) showing up in the "connected device list". Strange, never saw that before.
I clicked on the Icon for more info in the asus webgui and then I saw it was actually the Orbi Router which was showing up under the same IP as the asus router.
During all that the satelite node was perfectly fine, the orbi wifi was working, Internet was available, and the satelite nodes webgui was available as well.
The asus was still accessible under this mentioned ip, the orbi was not.
After that I did the following.
- disconnected the Orbi System
- connected to the asus web gui.
- Set the asus base IP (192.168.1.1) to 192.168.1.2 since the Orbi Router Node seemed to force itself to 192.168.1.1 as well.
- Set the asus dhcp range to start from 192.168.1.5 instead of starting at 192.168.1.2.
- the asus automatically cleared and rebuilt its IP / DHCP tables after asking me If I wanted to do so.
- Connected the Orbi Node again.
- As I had hoped it got assigned its "standard" dynamic IP from the Asus Router.
- Now I was able to login to the Orbi Router WebGui.
- The Orbi was still in AP mode - good.
- The Orbi was still set to get a "dynamic IP" from the connected Router.
- I disbaled Beamforing an MU-MIMO.
- I went back to the asus Web Gui and assigend the MAC Adress of the Orbi Router node a fix IP opposed to assigning this task to the Orbi directly.
Now the Router is up an running again. Lets see for how long.
I can return it for 12 more days - If I get a Problem again i ll do that and set up another asus 88u downstairs with probably a bitt less coverage but around 200 Euros cheaper.
I can accept the fact of the asus stuff member saying that there are thousands of wifi enabled devices around. But its either there hardware failling or IOs devices having big problems. I am not reading about other problems, or am I missing it?
So my bet is on the Orbi system having a few severe problems.
We got 8 IOS devices here as well, several media players, sonos, TVs with netflix and/or amazon, NAS, streaming movies and music all over the place.
Sorry for the bad english and hijacking this thread. maybe someone else can work a bit with my infos.
Have a nice sunday everyone.
I've had the Orbi now for roughly 3 months. It was working fine with my wireless clients up until recently. Maybe the past 2-3 weeks. Sometimes websites just don't load or I get some weird DNS error. After a minute everything is fine. Most of my devices are connected to the satellite. Earlier today it was pretty bad and a reboot of the router fixed it. Really hope Netgear fixes stability for Orbi. I've been recommending it to family and friends because of the great performance, but stability is much more important than performance.
I am going to try a factory reset to see if that helps. I'm on 1.9.1.12 btw