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
Actually, we did get somewhere much faster than we thought. My apologies for not responding to the forum yesterday. I did receive a response from someone higher in the food chain. I am hoping to see some real progress next week and possibly the week after. To show respect to the person I am interacting with I will not share their name, only to say it is the product manager. Given my experience in the tech world, the product manager is a good person to work with, and that person "typically" has enough status to make some waves and get stuff done.
I hope everyone is having a great weekend. Enjoy your Sunday, and may your Monday not be too hard for you.
Cheers….
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
NaderA for non-networking engineers Orbi and especially Orbi Pro have a long way to go. Chime back when Orbi Pro is a business class product like the Insight manageable switches and WAC. Hint: VLAN support. by VLAN RSTP, ... user friendly Mesh (just "throw in" wireless, wired, on whatever switch, no problems with network switch STP, in whatever combination, no need to configure wired or daisychain or spoke or whatever interesting things non-network-engineers do - these things must be done automatically. So you see .... I was never involved in Orbi or Orbi Pro Beta .... otherwise Netgear would have heard a lot of noise. Any kind of combination must be possible - a consumer "just" want to plug a cable, a wire, a switch, and does not want to care about whatever design limitations and configuration requirements. Any "random" installations of Orbi/Orbi Pro satellites must be possible. Take a Orbi router, two satellites and set-up. Need to extend the satellite in the barn with a switch and another satellite ... just plug it. And so on.
And for the network engineers: Please provide configuration information so their switches STP and RSTP and MSTP switched networks are not messed up along with the Orbi addition to the network.
You don't have to be a network engineer to set-up an Insight Network and have properly set-up network, with multiple wireless, VLAN, correct networking.
There is nothing that stops NTGR from making Orbi Pro properly using VLANs instead of the consumer L2.5 filter, only causing issues. And the way I everyone here understood the "tell us what we have to enhance" was taken as a word. Fact is - we got nothing. No problem, we will continue to push Insight even more to customers disappointed with Orbi Pro.
When will the BR500 be ready to be a business router by the way - I mean beyond of the Orbi-like-four-per-port-"VLANs"? Probably never. Face it: It's simply the wrong platform for a business class product. That's why Orbi Pro does not make progress, too.
We need a real security appliance for the Insight product line, not a poorly customized consumer board in an even worse designed rack mount enclosure.
Flash008 ibmman69 - food for thought.
Regards,
-Kurt.
PS. As of now, the WAC540 SSID VLAN config does not work (probably related to the static LAG) - only the first SSID and VLAN works reliably, anything else goes mad. Similar, the to members of the WAC540 don't properly identify on the link layer LLDP-MED does only work on the second, non-PoE interface. Asking for months to get this fixed ... business products, yeah.
Sorry, but I could not disagree with this stement more.
The features you pointed out in this reply are extremely basic and featured on most home/consumer routers. That they are not included on a "business" focused router is rather dissapointing.
It's my understanding (and I could be wrong) that the Orbi Pro OS/Software is based on OpenWRT. If that is the case, the code to do these things is already there. This should just be a case of enabling features then mapping them in your GUI.
Why not just open up the command line for us so we can do this ourselves? or give us an open source version of the firmware so we can add packages and save them so they won't be lost with every reboot? If we go in via telnet and try to make changes the permissions on the root drive reset and writing becomes impossible. Why? Do you have any idea how many of these you would sell if you let owners (us, the ones that paid for these devices that initially advertised they could do much of what we are requesting) install and config the packages we want?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
