2

Hairpin NAT/NAT loopback Trouble

I'm having trouble utilizing the hairpin NAT feature. I'm trying to access my NAS from inside my network with my external network address. I have all the port forwards setup properly. If I didn't, I can't even access the NAS from outside at all. Is there anything else that needs to be setup in order to do this? The blog post on this feature states that the port forwarding is the only setup needed.

I'm running eeroOS v3.9.2-18.

17replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Assuming all is set up correctly, try restarting the eero system.  There is a small, but rarely encountered bug with loopback that has been around for a while.  Restarting the system from the app usually resolves it for me, and luckily it rarely shows up.

    Reply Like
  • Just tried rebootong the routers. Still no luck.

    Reply Like
      • txgunlover
      • txgunlover
      • 7 mths ago
      • Reported - view

      schmatt It's not the bug then.  My loopbacks work 99% of the time, only had the bug show up about 4 times in the past 11 months.  Some of the common things: (assuming dynamic IP) make sure your dynamic IP client is correctly reflecting your current IP.  What IP does DNS return for the host name you're using?

      Reply Like
      • schmatt
      • schmatt
      • 7 mths ago
      • Reported - view

      txgunlover It's sort of working. I can access my external VPN address and connect fine. However, when I try to access my external website, I get a connection refused. Both are using the same named address. I'm not sure why I'm getting different results here. This also shows that the IP referenced by the name is correct. I have my NAS regularly checking and updating to the correct IP, if it happens to change.

      Reply Like
      • txgunlover
      • txgunlover
      • 7 mths ago
      • Reported - view

      schmatt I'm assuming both ports are forwarded (VPN & Web server)?

      Reply Like
      • schmatt
      • schmatt
      • 7 mths ago
      • Reported - view

      txgunlover Sorry, false alarm. In my messing around trying to determine to issue, I deleted the port forwarding for the webpage. It works now. It may have been the bug you were mentioning before. All is well now. Thanks for the help!

      Reply Like
  • Reboot doesn't fix the issue everytime. Even sometime it fixes, the issue still comes out after a while. My case 1 or 2 weeks. 

    Reply Like
  • I have this same issue as well.  Do you know if this will be addressed in a future firmware update?

    Reply Like
  • This was working,  but on the last versions of the firmware they brake it!!!

    Reply Like
  • Is Eero going to fix this anytime soon?

    Reply Like
    • mikeyunk I've been in contact with support regarding this and the forwarding issue.  They've acknowledged both, but haven't mentioned a date they'll be resolved.

      Reply Like
      • mikeyunk
      • mikeyunk
      • 1 mth ago
      • Reported - view

      txgunlover Thanks for the update.

      Reply Like
  • eeroOS 3.12.1 here experiencing hairpin NAT failures more often than usual. Today rebooted router to get loopback NAT working (which succeeded... for about 2 minutes). Prior to this I could go weeks and sometimes months between restarts.

    Reply Like
    • churusaa 3.13.0 fixes it.

      Reply Like
  • Hi txgunlover I'm not seeing the 3.13.0 version, at least on iOS.

    Reply Like
    • juampick It hasn't gone General Release yet.

      Reply Like
  • So when will 3.13.0 be available and can we test the beta now?

    Reply Like
Like2 Follow
  • 2 Likes
  • 3 wk agoLast active
  • 17Replies
  • 372Views
  • 6 Following

Need Help? We're here for you!

We're big on support, and we want to make sure you always have the best eero experience possible. Here are several resources you can use if you ever need our help!


Quick links

Community Guidelines

Help Center

Contact eero support

@eerosupport

eero.com