×  Introducing Nighthawk RS700 WiFi 7 (BE) Router. For more details, please visit Nighthawk Tri-Band WiFi 7 Router.

AX2400/RAX29 - hairpin/loopback NAT issue?


AX2400/RAX29 - hairpin/loopback NAT issue?

Just bought a new Netgear AX2400/RAX29 and updated to the latest prompted firmware (V1.0.6.74_1), but it seems that hairpinning has stopped working?  I host a  couple of small services on my network, and port forward  the tcp port to the outside.  The port forward works exactly as it should from the outside world, however, internally, I should be able to use the same address to reach the internal server.  Every netgear product I've ever owned did hairpinning fine, but for some reason, this RAX29 doesn't.  To be honest, I thought I had tested it before the firmware update, and I thought it was working, but clearly after the firmware update, it doesn't.  If I could  get a copy of the original firmware even, I could flash it back to that.


Obviously, the workaround would be to add an entry to my hosts file and use DNS to resolve to the local IP, however, I'd like to get the hairpinning/loopback working if possible.   I may try a factory reset tonight to see if that does the trick. 

Message 1 of 3

Re: AX2400/RAX29 - hairpin/loopback NAT issue?

I've never used that feature but if yoou want to go back in firmware versions, you can get them from


Click on the big + in the left corner to expand
Routing: NETGEAR RAX43 - Firmware: v1.0.15.128 (1 Gbps down, 40 Mbps up)
Switching: 2x NETGEAR 8-ports (GS108v4) / 1x NETGEAR 16-ports (GS116v2)
Desktop: AMD Ryzen 9 5900X - Server: Intel Core i7-7700K - NAS: Intel Pentium G4400, 20 TB
Message 2 of 3

Re: AX2400/RAX29 - hairpin/loopback NAT issue?

Thanks for the tip.  I did try going back to the oldest firmware listed on that page, and the problem still exists.  As a workaround, for the time being, I figured out that it's only when the internal/external port were the same, that I'm having a problem.  If the router is translating to one port to another, oddly enough, it works just fine.  So, instead of listening on port 8080 internally and externally, I changed the internal port to listen on 8079, and externally left it to 8080, and it seems to work.  Definitely seems like a glitch in the firmware.  If I have time, I'm still considering to a factory reset, to see if that works.

Message 3 of 3
Discussion stats
  • 2 replies
  • 0 kudos
  • 2 in conversation

Orbi WiFi 6E