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
st_shaw wrote:RogerSC The most recent firmware (1.12.0.18) removed the ability to turn off 2.4 GHz and adjust power levels. Also, the Orbi ALWAYS has an active hidden SSID on 2.4 GHz (on the same channel) even when 2.4 GHz is turned off. Lastly, if you select the 20/40 MHz coexistence setting, then Orbi will fallback to 20 MHz if it detects another AP with overlapping channels.
That's why I was trying to configure the Orbi as an AP with the previous firmware release...to be able to turn off 2.4GHz. wireless, which was lost with the latest. Can't do anything about "hidden" SSID's :-), but I'm not using 2.4GHz. wireless, none of my clients need it or connect using it. And yes, I always have 20/40MHz. coexistence checked, and sometimes it falls back to 20MHz., sometimes it doesn't. This isn't my first rodeo with Netgear routers :-). My hope was that when the Orbi was set up as an AP with the previous firmware release, that it wouldn't auto-update to the latest, that it would just be stable. Part of that was to restrict the AP's access to Netgear's firmware servers in the main router, which I also tried to do. I think that the other poster's success with AP mode may be more to do with their main router using dd-wrt firmware than just having the Orbi in AP mode.
Anyways, I may try again, since I'm thinking that with all the jerking around that I had to do the settings on the Orbi may have gotten corrupted. And that may be why the settings on the router said that 2.4GHz. wireless was off, but it was actually on when I finally got the Orbi in AP mode with 2.4GHz. wireless turned off in the settings. I'm thinking that because when I gave up on the AP effort and went back to router mode with the Orbi, it didn't work for me until I reset both units and manually reconfigured them. Now the Orbi is working fine in router mode with the latest release, and I have a saved set of "clean" settings.
At this point, hoping that Netgear gets the removed functionality back in the Orbi firmware. As well as allowing me to pick a particular firmware release if I have a reason to do so.
Interesting thing! First, I was dissapointed as I lost functionality from auto-update today from a firmware downgrade 2 days ago.
However, fiddling around with the settings, I got the satellite to be recognized under the new firmware!
(Note: What works for me may not work for you)
- 1. Advanced Setup > Wireless Setup > Wireless Settings > 2.4Ghz (Auto) > Set to "11".
- 2. Advanced Setup > WAN Setup > NAT Filtering > Secured > Set to "Open".
I'm not sure which of those two got satellite functionality back for me but all what I do know is, it's all working. Good luck to you all.
Ucchi wrote:Interesting thing! First, I was dissapointed as I lost functionality from auto-update today from a firmware downgrade 2 days ago.
However, fiddling around with the settings, I got the satellite to be recognized under the new firmware!
(Note: What works for me may not work for you)
- 1. Advanced Setup > Wireless Setup > Wireless Settings > 2.4Ghz (Auto) > Set to "11".
- 2. Advanced Setup > WAN Setup > NAT Filtering > Secured > Set to "Open".
I'm not sure which of those two got satellite functionality back for me but all what I do know is, it's all working. Good luck to you all.
Can anyone comment on the security implications of item #2, above?
gbjackson wrote:
Ucchi wrote:Interesting thing! First, I was dissapointed as I lost functionality from auto-update today from a firmware downgrade 2 days ago.
However, fiddling around with the settings, I got the satellite to be recognized under the new firmware!
(Note: What works for me may not work for you)
- 1. Advanced Setup > Wireless Setup > Wireless Settings > 2.4Ghz (Auto) > Set to "11".
- 2. Advanced Setup > WAN Setup > NAT Filtering > Secured > Set to "Open".
I'm not sure which of those two got satellite functionality back for me but all what I do know is, it's all Thworking. Good luck to you all.
Can anyone comment on the security implications of item #2, above?
gbjackson@ - The "Help" button at the bottom of the page states the following: "This option determines how the router deals with inbound traffic. The Secured option provides a secured firewall to protect the PCs on LAN from attacks from the Internet, but it may cause some Internet games, point-to-point applications, or multimedia applications not to work. The Open option, on the other hand, provides a much less secured firewall, while it allows almost all Internet applications to work."
Have you ever looked at the logs under the "Administrative" tab, and noticed all of the DOS attacks? A bit concerning. So for me -- I'll leave mine checked as "Secured".
I switched the WAN (NAT) setting back to secure.
Further fiddling around with the 2.4ghz wireless channel settings, I was able to get the sattelite recognized only when using Channels 10, 11.
So there might be the solution: Don't use (Auto) and find which band on the 2.4ghz channel works for you.
DarrellRiffe - thanks. It would be nice if Netgear provided some detail regarding the "much less secured firewall" statement. I know that NATfiltering can be a problem for certain applications (online gaming, etc...), but it's not clear exactly what you're doing when you set it to open? Are you effectively disabling the router's firewall, or doing something a little less drastic. Point taken about the logs, although when I ran some security tests with the router set to "secured" and then to "open," there weren't any differences.
gbjackson wrote:
DarrellRiffe - thanks. It would be nice if Netgear provided some detail regarding the "much less secured firewall" statement. I know that NATfiltering can be a problem for certain applications (online gaming, etc...), but it's not clear exactly what you're doing when you set it to open? Are you effectively disabling the router's firewall, or doing something a little less drastic. Point taken about the logs, although when I ran some security tests with the router set to "secured" and then to "open," there weren't any differences.
My understanding is that setting NAT filtering to open is the same as full-cone NAT, as explained in this article, while secure NAT is either restricted cone NAT or port-restricted cone NAT (I haven't tested to determine which, but it's like port-restricted NAT).
Setting NAT filtering to open does not completely disable the firewall. Any closed ports will still be inaccessible. The router wouldn't know where to send the traffic because your LAN is a private subnet. A device on your LAN would have to initiate an outgoing connection first in order to open a port. Once that happens, and if NAT filtering is open, then any device on the Internet can access that port on that LAN device.
I hope this makes sense. It can be confusing.
