NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Is NAT loopback supported on Netgear Orbi RBKE963
Hi all, First time posting here, nice to meet you all. I want to purchase a Netgear Orbi RBKE963 or the B (black) version. I have one specific requirement: - Does it support NAT loopback?...
Thanks for the explanation. Disappointing to be sure. ☹️
I had considered using port forwarding to provide access to security cameras and decided it was "too much detail" for me. Since any given port (or range of ports) can be forwarded to only one internal IP, that meant I would have to define (and remember) separate external port numbers for each camera that would forward to the internal port number on different internal IPs.
Such as, supposing the internal port was 9000:
- Camera 1 would be public IP port 9001 forwarded to internal IP port 9000
- Camera 2 would be public IP port 9002 forwarded to internal IP port 9000
- Camera 3 would be public IP port 9003 forwarded to internal IP port 9000
- and so on.
While I am OCD enough to have worked this out and created browser bookmarks for each camera, I was already using the manufacturer's "cloud app" when away from home, so being able to access cameras from home with both LAN IP and NAT Loopback just wasn't worth the effort. I only use NAT Loopback to verify that port forwarding is working.
Appreciate you taking the time to report your results. This still begs the question of why Netgear would remove a feature that existed in every previous router model.
CrimpOn wrote:Thanks for the explanation. Disappointing to be sure. ☹️
I had considered using port forwarding to provide access to security cameras and decided it was "too much detail" for me. Since any given port (or range of ports) can be forwarded to only one internal IP, that meant I would have to define (and remember) separate external port numbers for each camera that would forward to the internal port number on different internal IPs.
Such as, supposing the internal port was 9000:
- Camera 1 would be public IP port 9001 forwarded to internal IP port 9000
- Camera 2 would be public IP port 9002 forwarded to internal IP port 9000
- Camera 3 would be public IP port 9003 forwarded to internal IP port 9000
- and so on.
While I am OCD enough to have worked this out and created browser bookmarks for each camera, I was already using the manufacturer's "cloud app" when away from home, so being able to access cameras from home with both LAN IP and NAT Loopback just wasn't worth the effort. I only use NAT Loopback to verify that port forwarding is working.
It absolutely was a PITA with the Orbi's NAT configuration page. Slow and cumbersome.
OPNSense allows you to define aliases for ports, port ranges, hosts, address ranges, and other things that make it much simpler to configure NAT and other firewall rules. You can also enable its nginx plug-in as a reverse proxy that lets you route a URL path to a specific IP address/port combination. I haven't actually played with this yet, but I know it's possible.
Appreciate you taking the time to report your results. This still begs the question of why Netgear would remove a feature that existed in every previous router model.
You mean like the ability to assign separate SSIDs to 5GHz and 2.4GHz radios? And network isolation between VAPs*? Nah, they'd never do such a thing ... 😡
* The IoT WLAN is directly connected with the "main" LAN/WLAN. No protection from bargain-priced foreign hardware that might have less than honorable intentions on your network.