NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmware 2.3.1.100
I am not sure what to say about this new firmware. My parents alway taught me, “If you don’t have something nice to say, then say nothing at all”. Yet, I was also taught, “if you have a probl...
All,
We have received a list of comments from Flash008 and are reviewing them. Please note that there is nothing in the world that makes us happier than seeing happy and satisfied customers and users of our products. At NTGR, we take pride in our products and seek to please our customers.
In regards to the response that MrJosh provided, his point is that Orbi Pro was designed to be a DIY product for business owners that are not network engineers. I has the features to meet the needs of that group of users. But it looks like the success of the product, has resulted in unforseen expectations for features such as SNMP or Syslog which is not something that a small business owner would require.
in other words, Orbi Pro was not meant to replace a product like our WAC540 that has all kinds of bells and whistles.
Please bear with us as we are going through all the comments received which is a summary of all of your points and we'll have a dialogue and work through them.
Finally, we are doing our best to wow our customers, but please don't interpret this as commitment to implement features.
Orbi Pro Product Management
Just want to put this thread back on track...
We were dicussing features that we feel should be included in the ORBI Pro product. This includes features that were initially stated in the documentation but later pulled out of "revised" documentation and never implemented.
Has anyone received an official reply from far up the Netgear executive chain? I'm going to have to switch products soon, and not just my network but some of my customers as well.
Throwing out this idea one more time as well... the Orbi is using DD WRT underneath. Many packages can be applied to the Orbi after you SSH/Telnet in. The problem is that you cannot write to the boot partition so all changes are lost with reboots are powering off. Why not just offer a patch that allows us to "write" properly so we can fix most of these issues (quickly and pretty easily) ourselves? We could probably clone whats in the Orbi now to our own storage and make this happen, but we shouldn't have to do this.
-ShawnC
Ironic it may seem. I just received communication from Nadar. Nader just returned from vacation and it "catching up" on things. Nadar assures me this is not a dead topic.
It is my opinion that "time is better" for this situation. Unlike others who will give you a fast, but meaningless, response. I believe Netgear is taking this very seriously and working on their response and solution to this. Of course, this means "TIME".
So, let us wait for Netgear's response which should be "soon".
I hope everyone had a great weekend and a Happy 4th....I spent the last 5 days on the beaches of Santa Monica, CA, trying very hard to not care about a damn thing.....LOL......And I did a great job doing it.
Hello Everyone,
Just got an update on engineering regarding the issue folks are seeing regarding the duplicate SSID's being broadcasted. The current release does not have the fixes included and are included in the upcoming 2.4 Orbi Pro release scheduled in the middle of August. Current release was to resolve throughput issues that were reported.
MrJoshW wrote:The current release does not have the fixes included and are included in the upcoming 2.4 Orbi Pro release scheduled in the middle of August. Current release was to resolve throughput issues that were reported.
Seriously?!?
This is supposed to be a security issue - major in my opinion - requiring a fix within a few days. This is not consumer Orbi or Nightmare junk (where Netgear does not bring any feet to the ground hunting bugs anyway) is it?
I agree, how can we leave our company network exposed like this for a month?
We need a quick fix adressing this issue!
The issue with the duplicate SSID is due to selecting the option to split both wireless bands to their own seperate SSID in the wireless 2 profile. Even if you choose not to broadcast the 5ghz band the SSID will still be displayed. The work around currently for this is to either not use the split wireless bands option or to use a password on both 2.5 and 5 ghz SSID. Engineering has acknowledged this issue and is planning to address this in the upcoming Orbi Pro 2.4 release.
Actually, I never set my Orbi Pro to separate bands. In my case the wired backhaul seems to have been the trigger for the new band posting a duplicate wi-fi profile 2 network without any security. Thus, this was a startling and aggregious security problem that leaves me thinking Netgear needs help testing solutions before they go live. I enjoy the equipment enhancements (especially being able to use all wi-fi bands for clients) but knowing my private network was open was unacceptable and I am glad I found it after a week or so and that it seems to have caused no intrusion for me before I did find it. Others may not be so lucky.
One more thing, I see that version 2.3.5.108 is now out. I updated but in reading the update notes I see no mention to this major security problem as a known issue. This is again making me lose trust in Netgear. Why don't they admit that people are vulnerable to an open network on profile 2 if they are using backhaul. This is clearly a known issue unless that was fixed in 108 which they are not saying it was. Boy, this upsets me something fierce as security is critical as this means some people's presumptively secure work networks will be left open for any wi-fi open network surfer to find. This is a major blow for confidence in Netgear.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
