NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FishDawg
Feb 12, 2022Aspirant
Orbi NAT Hairpinning/Loopback Not Working
I have the Orbi RBR750 router.
I set up port forwarding as well as dynamic DNS. Everything works as expected when connecting to servers on my local network using that DNS name and port number when connecting externally. I can connect from outside my home network. I can of course also connect to the servers on my local network using their local IP address.
However, I cannot connect to them from my local network when using the DNS name (or external IP address). My understanding is this should work due to a feature called NAT hairpinning or NAT loopback.
I see Netgear says my router supports this feature according to this page: https://kb.netgear.com/000049578/Which-NETGEAR-routers-support-NAT-loopback. I have the latest firmware (V4.6.5.14_2.0.54). Yet, it is unable to connect.
How do I get this working?
8 Replies
Replies have been turned off for this discussion
I can verify that NAT loopback works on the (older) RBR50 Orbi. Some possibilities come to mind:
- What port is being forwarded? I have a vague memory of certain ports being "special" to the Orbi router. (my memory is not that great. On my RBR50 the 'drop down' menu for port forwarding includes http (80) does not include https(443). Are you trying to forward 443?
i.e. does the specific port number make a difference? - What DNS service is being used to resolve DNS names? I just now attempted to reproduce this error on my RBR50, by forwarding port 80 to one of my Pi-hole servers. My PC is not using Orbi to resolve DNS. (using CloudFlare and Google instead). Got some goofy error message that access to http://<my-DDNS-name> was denied. What this appears to be was that somehow the DDNS request got 'NAT-looped' to my Pi-hole, which threw a fit. I swear that I have done this exact experiment before to demonstrate that NAT-loopback 'works'. Now, I am confused (and unhappy).
- Can the problem be duplicated on another Orbi 750? Alas, only some nice volunteer who watches the forum and has a 750 could do this.
- The 750 firmware may be broken. There have been plenty of issues raised about the 750 firmware. This might be yet another problem. (Do I remember correctly that there is 'beta' firmware going around for the 750?)
- FishDawgAspirant
Your comments got me thinking. Thanks for the suggestions. I tested out the things you suggested, but couldn't find an answer.What port is being forwarded?
I tried a few ports and it didn't help.What DNS service is being used to resolve DNS names?
I tried changing this and it didn't help.I really meant to ask, "which port?" as in 443? 80? what?
The original post mention port(s), i.e. more than one.?
- What port is being forwarded? I have a vague memory of certain ports being "special" to the Orbi router. (my memory is not that great. On my RBR50 the 'drop down' menu for port forwarding includes http (80) does not include https(443). Are you trying to forward 443?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?