NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmware V1.12.0.18 Discussion
This does indeed appear to be based on (identical to?) the last private beta V1.12.0.16 and has been released to the public. Hope it helps!
Guest mode AP isolation finally works 100% over IPv4...
New Features and Enhancements:
- Supports ReadySHARE Printer for Orbi devices that are equipped with a USB port
- Updated the OrbiOS API to v3.14
Bug Fixes:
- Fixes the iOS disconnection issue.
- Fixes the Dropcam disconnection issue.
- Fixes the convergence issue when an Ethernet connected device moves from one Orbi to another.
- Fixes the issue where the Orbi app can’t find the Orbi router if the router is using IPv6 and is in AP mode.
- Fixes the issue where the Orbi app can’t display more than 20 connected devices.
- Fixes the issue where the installation assistant might not display if the device is connected to the Orbi network wirelessly.
- Fixes the issue where the 2.4 GHz backhaul setting is disabled if the fronthaul MU-MIMO and TxBF is disabled.
- Fixes the issue where IPv6 devices on the guest network can access the Orbi router’s web GUI.
- Includes security fixes for the following security vulnerabilities:
PSV-2016-0133, PSV-2017-0607, PSV-2017-0615, PSV-2017-0736, PSV-2017-2190
Download Link:
RBR50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBR50-V1.12.0.18.zip
RBS50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBS50-V1.12.0.18.zip
So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
nxc wrote:So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
So it's been five days, and everything has been rock solid. Again, your mileage may vary, but updating to v1.12, wiping NVRAM settings via telnet and subsequently performing a factory reset, and never using the built-in Speedtest seems to have fixed my issues. My satellite doesn't appear to have dropped connections, the satellite is currently handling about 1/3 of the devices on my network, and my speed test results (from the website -- NOT THE ADMIN) are fantastic:
This is approaching the effective limit of what you can expect from a modern iOS device. I'm very happy with the results. Orbi is finally living up to its reviewer reputation.
nxc wrote:
nxc wrote:So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
So it's been five days, and everything has been rock solid. Again, your mileage may vary, but updating to v1.12, wiping NVRAM settings via telnet and subsequently performing a factory reset, and never using the built-in Speedtest seems to have fixed my issues. My satellite doesn't appear to have dropped connections, the satellite is currently handling about 1/3 of the devices on my network, and my speed test results (from the website -- NOT THE ADMIN) are fantastic:
Well what do you know, this seems to have worked for me too. NVRAM reset, follow by factory reset. Reconfigured everything manually and it's working fine so far. Before I could only get 70-80Mbps wired to the router, now I'm gettting 800Mbps+. I'll do some testing later to see if I can narrow the cause of the issue down, starting with the speed test which has some broken QOS settings hidden behind it.
- I agree with the theory about the speed test impacting QoS.
- (Sorry hit post by mistake)
I think that there is a dynamic QoS service on the router that only kicks in once the speedtest is run. (That would be in line with other net gear routers I think. )
Trouble is that the dynamic QoS seems very aggressive and/or not working properly so I also don't run the speed test for exactly that reason.
scornwell wrote:
nxc wrote:
nxc wrote:So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
So it's been five days, and everything has been rock solid. Again, your mileage may vary, but updating to v1.12, wiping NVRAM settings via telnet and subsequently performing a factory reset, and never using the built-in Speedtest seems to have fixed my issues. My satellite doesn't appear to have dropped connections, the satellite is currently handling about 1/3 of the devices on my network, and my speed test results (from the website -- NOT THE ADMIN) are fantastic:
Well what do you know, this seems to have worked for me too. NVRAM reset, follow by factory reset. Reconfigured everything manually and it's working fine so far. Before I could only get 70-80Mbps wired to the router, now I'm gettting 800Mbps+. I'll do some testing later to see if I can narrow the cause of the issue down, starting with the speed test which has some broken QOS settings hidden behind it.
Can somebody explain the steps needed to perform this with a Mac? I'm aware of the Mac Terminal application, and can use it to get to Telnet. I just can't seem to figure out how to use Telnet to connect to the Orbi Router. I've tried "Open 192.168.1.1" and "Open orbilogin.com...", but the connection is either refused or timed out.
Go to the debug page on your router to enable telnet. http://ROUTERIP/debug.htm
From the mac terminal type "telnet ROUTERIP"
Return to the debug page and disable telnet when finished.
Well, it has been six weeks since I disconnected my Orbi system waiting for a new firmware update, but after reading this latest text:
Enable telnet and sign into the router.
nvram erase
nvram commit
rebootI decided to give it a try and so far, so good with the latest firmware release, following these instructions.
Thanks to all for providing this information. It has made a difference and now use my Orbi and wait for the next offical v.2.0 release!
Cheers!