NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rhester72
Jul 11, 2017Virtuoso
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...
- Jul 11, 2017
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
nxc
Aug 28, 2017Apprentice
scooterman2 wrote:Am a little over my skis - am running off a mac. When I go to http://ROUTERIP/debug.htm, I get a 404 (file or directory not found) error. When I got terminal, I get ot he routerip directory but get the following error - routerip: nodename nor servname provided, or not known.
Any advice on how to proceed?
Thanks
You need to replace "routerip" with the actual IP address of your router, which by default will be 192.168.1.1
scooterman2
Aug 28, 2017Tutor
Thanks. when I go to terminal and type: "telnet orbilogin.com", I get this error:
telnet: connect to address 192.168.1.1: Connection refused
telnet: Unable to connect to remote host
what is supposed to happen? When I go to IP address/debug.htm, I get the Orbi frame of the page and then a spinning circle and Please Wait message.
I am not very familar with telnet.
- RogerSCAug 28, 2017Virtuoso
scooterman2 wrote:Thanks. when I go to terminal and type: "telnet orbilogin.com", I get this error:
telnet: connect to address 192.168.1.1: Connection refused
telnet: Unable to connect to remote hostwhat is supposed to happen? When I go to IP address/debug.htm, I get the Orbi frame of the page and then a spinning circle and Please Wait message.
I am not very familar with telnet.
Yes, you need to enable telnet on the router. Just go to:
orbilogin.com/debug.htm
and when that comes up, click on the "Enable telnet" box. Then you'll be able to telnet into your Orbi router.
If you want to telnet to your satellite, just get the satellite IP address out of the "Attached devices" list from the Orbi web admin GUI, and go to:
<satellite IP address>/debug.htm
and enable telnet for that. Here "<satellite IP address>" would be replaced by something like 192.168.1.101 or whatever your satellite's IP address is.
Don't forget to go back to the debug.htm interfaces and disable telnet when you're done using it.
- RogerSCAug 29, 2017Virtuoso
scooterman2 wrote:Thanks. when I go to terminal and type: "telnet orbilogin.com", I get this error:
telnet: connect to address 192.168.1.1: Connection refused
telnet: Unable to connect to remote hostwhat is supposed to happen? When I go to IP address/debug.htm, I get the Orbi frame of the page and then a spinning circle and Please Wait message.
I am not very familar with telnet.
Ah, sorry, I see that I didn't read quite far enough...you did try to enable telnet, but the debug.htm page wouldn't open. In that case, I'd suggest turning off both the router and satellite, and the turning them back on (power-cycle both units). When they come back up, try the "orbilogin.com/debug.htm" again, and it should come up. Then you can enable telnet to the router.
- scooterman2Aug 29, 2017Tutor
Thanks. Will try that in the later and hopefully that does the trick. Appreciate the clarification.