NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Feature request (force a device to a specific Orbi)
I have one problem device that, for some reason, always chooses the Satellite Orbi instead of the Router Orbi, which is always the furtherest away from the device. The Router Orbi is by far the closer one to the device. I can reboot the network and the device will connect to the Router, but will eventually creep back to the Satellite for whatever reason. It's a stationary device (TV) and never moves. I'd like to request to have a feature implemented that will allow us to "force" or designate a specific device to a specific Orbi. I know they plan on releasing a firmware that will allow us to customize how the lights on top act (always on, etc), which I hope gets released soon! Also, a Guest Network feature would rock!The 2.1.2.18 nightmare
I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your money. I just wanted to tell everyone if you hate 2.1.2.18 as much as I do (well hate isn't the word, it just physically BREAKS my entire wired network... nothing wired has a connection NOTHING. I verified it 2 times because I reverted back to 2.1.2.16, when it was all working ok. Then it decided last night to RE-DOWNLOAD 2.1.2.18. You would think if you manually tell a product to revert back it wouldn't just re-do it. This is so dumb, my computer is hooked to a switch, that is connected to Orbi... when it updates to 2.1.2.18 I have to disconnect my computer from the switch because it breaks EVERYTHING on the switch nothing gets an ip... I have to connect directly to the orbi from my computer, I have to disconnect all the other wired connections to the orbi. Then I downgraded the firmware ONCE again, then I telnet into the router to change the NVram to not let this piece of crap update itself. That is my solution Netgear. A consumer had to do all that stuff because your firmware BREAKS everything. This started with me being angry at Google for breaking everything, now I blame netgear. It isn't my switch or any of my wired stuff, because it all magically works perfectly on 2.1.2.16. But the second I upgrade it all breaks, I even did the factory reset 2x, nothing wired works.. the funny thing is my switch is a netgear switch too... I have NEVER in my life had such a complicated product to keep running. In case anyone else is dealing with the same problems, below is how to telnet and stop it from updating. This is my only solution, I have absolutely 0 ZERO confidence in any firmware update from Netgear... based on a 100% failure rate: 1) Launch your favorite web browser and go to <Router IP Address>/debug.htm 2) Login <username> <password> when prompted 3) Check Enable Telnet 4) Start a Telnet session. I use Putty. Enter the <Router IP Address> Telnet is using port 23 5) You can skip this step if you like. I am calling it out for illustration purposes only... Type nvram show | grep auto_* <ENTER> You will see a list similar to this: root@RBR50:/# nvram show | grep auto_ vpn_access_mode=auto wl_auto_antenna=1 set_auto_agreement=0 orbi_auto_upgrade=1 ipv6_autoConfig_dns_assign=0 ipv6_autoConfig_dns1= ipv6_autoConfig_dns2= upnp_enable_autoScan=0 ipv6_auto_dns_assign=0 bas_auto_conn_flag=0 orbi_auto_upg=0 autofw_port0= ipv6_auto_dns1= ipv6_auto_dns2= qos_auto_bandwidth=0 green_enable_autorefresh_status=0 enable_dev_auto_refresh=1 wl_rate=auto auto_check_for_upgrade=1 auto_update=1 root@RBR50:/# root@RBR50:/# The 3 configurations highlighted above you will want to update the value from =1 to =0 orbi_auto_upgrade=1 auto_check_for_upgrade=1 auto_update=1 6) To update run the following commands: nvram set orbi_auto_upgrade=0 <ENTER> (no spaces after set) nvram set auto_check_for_upgrade=0 <ENTER> (no spaces after set) nvram set auto_update=0 <ENTER> (no spaces after set) 7) Type the following commands to confirm the 3 configurations are set to =0 nvram show | grep orbi_auto_upgrade <ENTER> nvram show | grep auto_check_for_upgrade <ENTER> nvram show | grep auto_update <ENTER> 8) After you confirmed the 3 configuration values are set to =0 then type nvram commit <ENTER> (this step will save the changes) 9) Type exit to terminate the telnet session 10) Go back to the <Router IP Address>/debug.htm web page and uncheck Enable Telnet Please note within a day or so the Orbi will know there is an updated firmware release available but it will not automatically install it. If you do go back into a Telnet session after the Orbi knows there is an updated firmware release the configuration orbi_auto_upgrade will have a value greater than 1. That is okay. Do not change the value back to =0How come ORBI still getting raving reviews? is Netgear paying them for good reviews and ignoring a l
How come ORBI still getting raving reviews? is Netgear paying them for good reviews and ignoring the phenominal number of users in this forum having issues. Those issues are real and sooner or later everyone is going to have them based on their needs (as it seems like with many users running fine for 6 months or so). ORBI is is a premium system and unless you have a box full of $$ sitting somewhere to buy gadgets, you bought ORBI for multi-streaming-devices (10+) and corner to corner stable WIFI. Both of which had failed by Netgear firmware. Don't take me wrong, ORBI hardware is still top notch and just need a good dedicated serious team of software devs and QA to do the right thing. I am a solutions architect myself and knows that the best solution is the one that fits your client needs and that may not always be the latest and greatest. https://www.tomsguide.com/us/best-mesh-router,review-5191.htmlBlocking inbound traffic by IP address
Just got an Orbi and am astonished that it is not possible to block inbound traffic by IP address, either explicitly (as a range), or from IP blacklists available from spam blocking lists. Being able to block incoming traffic by geographic region can be incredibly helpful, as many attacks originate in Russia in China. The fact that Orbi has DoS detection and gives me log entries like this "DoS Attack: SYN/ACK Scan" and no way to stop it is amazing. This topic has been raised in the past and it always gets closed with the statement that this is "beyond the scope" of a consumer level router and that only $1,000+ enterprise routers can do it. Bull. A $35 Linksys WRT54G running the open source DD-WRT firmware can do iptables blocks of IP addresses and ranges. A $250 Orbi should be able to do this without breaking a sweat.Orbi automatic restart on new firmware! 1.9.1.12
This morning, the ORB updated its firmware automatically and restarted again. I thought the system would usually prompt the user for update instead of auto update. Is there a feature not to auto update the firmware but allow user to confirm before updating? regardsI just had an epiphany... hear me out on 2.1.2.18
So you can read through all my anger and rant on 2.1.2.18. I have started several threads on how horrible this has been. But someone wrote something that made me think why I may be having issues with this firmware and others are not. First, when I install this firmware, it completely breaks all my wired connections. I have a netgear switch and everything behind that switch including 2 hubs will not get an ip. My main computer the same, I can't even log into the router to downgrade it. This all works perfectly fine with 2.1.2.16. But since Netgear has forced the update on me 3 times, I have confirmed everytime it is complete chaos when it updates, without fail. But one thing I didn't mention was that one of my orbi satellites is hardwired through the switch and hub that goes all the way out to the garage. I believe I read someone said their backhaul that was wired was giving them fits on 2.1.2.18, but when they disconnected it, everything was ok. So if anyone from Netgear is listening, maybe test that out. The weird thing is that 2.1.2.16 is just fine with the same configuration. But 2.1.2.18 just cripples my network. The symptoms are similar to that endless network loop if you plug a device into itself on the network. So I suspect something between the new firmware and hardwiring the satellite my be the issue. I cannot confirm as I am UNWILLING to go through the hell of 2.1.2.18 again, until the router forces it upon me again. I did change the NVRAM to tell it not to update, but it seems like it still did anyway the last time. The other funny thing I noticed on this new firmware is that I have a wired HP printer an x576. I gave it a DHCP address to make it static since I scan to it over the network. When I did it the Orbi firmware recognizes it as a sattelite. It lists under the attached devices sattelite. I don't think that is supposed to happen, once again Netgear, if you are monitoring this stuff (which I sincerely hope that you are, because you provide crap for customer service, so at least pay your people to read through all of us going through hell to troubleshoot for you), maybe you can test and check out those 2 issues. Anything behind my switch is completely dead everytime I upgrade to 2.1.2.18. I just also have that satellite plugged in and just thought of that when someone else posted about it. I didn't even get into my anger about Orbi and Google with all the stuff going on, I am just trying to solve one crazy issue at a time. It is very annoying to pay 1000.00 for a mesh system that I have to spend this much time diagnosing for a company who will not provide me any customer support.. very annoying. Get your stuff together Netgear... stop releasing half a$$ed firmware updates that are ridden full of bugs, and give customers the option to opt out of auto updates without having to telnet into NVram settings on the router. That is ridiculous.
