I too would like to add my vote for NAT Loopback / NAT Hairpinning. Set everything up last night, love the speed and range, but disappointed to find out that I cannot access my IP Surveillance System using my external DDNS address. Would really like to keep these instead of switching back to OnHub which did support loopback. Hopefully the team can provide an update; is this at least on the roadmap? 

Jeff C.

Agreed. I'm in the same boat. Need this badly!

+1000

Here is my request for this feature to be added! It's not preventing me from using the eero's but it's a PITA to work around it. 

I just got a set today and found out that it does not have NAT loop back feature . I need it for my security cameras. Is there a time frame for this to be implemented. I would like to keep the unit, but if the feature is not available anytime soon then I would go back with my old router.

Can some someone from eero advise?

Regards,

K

This is a growing need for eero users.  I have eeros installed at two homes and cant access (with knowing IP addresses or some internal DNS setup):

 - QNAP backup (they have an external dns service)

- Crestron home automation (they have external dns) - yes Zuckerberg uses this in his Jarvis home

- Several DVR/NVR security camera configurations

- Slingbox

I use an external ddns service from NOIP.com for a single address for each of these devices - would like to use this noip address inside of my house.

I must note, my eeros are arriving on Tuesday, and it sounds like they will immediately be returned. If I can not access them by putting in my public IP address or associated DynDNS hostname, I will not only be unable to use my 8 security cameras, but will also understand the mindset of eero. I am coming from Luma because of poor performance, but they at least support a fundamental understanding of networking.

Let's hope I have simply misunderstood, but this would affect 100% of security camera users, which of course are probably the bulk of your first round buyers and certainly your cheerleaders among your platform.

But on all routers I've tried (7+ in a year and a half), and on Luma this moment, I just leave my hostname (or public IP) in my camera app and I see my cameras on or off network. Only the Linksys EA9500 had a NAT Redirect feature I had to keep off for it to work. Every other router I've had or tried for the past 3+ years has worked out of the box with NAT loopbacks.

jalvani  I too use an internal DNS server, but it is spotty. Eero should add one.

Got the system set up and I am not impressed at all (TONS of WiFi drops...can not move through the house without a drop at least every few minutes, but that's a topic for a different thread). The issue here is while one app on Android (the fantastic TinyCam Pro) can support a home/away feature, the app I am forced to use on iOS does not. So, my wife, in-laws, and mother can not see the cameras properly when they are home (or away; depending on set up). 

Also note, the cameras are only one part. I have a number of Python apps that I access via ports (about 8) and there is no way I will tolerate multiple bookmarks or typing in the private IP address. Lastly, my wife, who also uses a few Python apps, does not even know what an IP is, much less remember which is what and so forth.

I have to be honest, I am appalled that a $500 router does not have what Linksys (and every single other router) has had since 2004. I don't want to be harsh, but the time and effort to get this system set up, and now have to go through the process to return is so dis-heartening.

I was an eero preorder customer and have overall loved the system, even if it's a little slim on features. But this is a must have feature for home automation, and is enough to move on to a competitor. Please, eero, address this fix quickly. It does not sound like a difficult addition and much simpler than the UI redesign work you keep pushing out.

I second the previous posters.  This is a feature that all my routers have supported over the years.  I can't believe this premium product does not support NAT loopback.  

Just throwing my $.02 in that I too would love to see NAT loopback supported in some way. I use a dynamic DNS service to allow me to connect to various apps on my computer from my phone when away from home. I hate not having that ability when I'm on my home wifi.

This is what I received from them today:

Raoul (eero Customer Support)

Feb 14, 1:49 PM CST 

Hello David, Currently customers would use a website interface or log directly into cameras, if using a device on the internal network. No Timeline for implementation of NAT-Loopback but will submit as a feature request.

Raoul @ eero

Another frustrated user.   A very basic feature, yet a $500 router won't support :(

Other than this, I would be a perfectly happy customer.

I just picked up my Eero mesh system from Best Buy yesterday.  After spending over an hour working through the app setting up all of my static IP addresses and port forwards, I was wondering why I could not access my Synology NAS and my IP cameras via DNS names when I came upon this thread.  I can't believe that these devices cannot perform such a fundamental feature that every other router that I have ever used has supported.  I have 13 more days to decide if I am going to keep it or if this is a deal breaker.  It would be nice to have some sort of ETA from Eero regarding this much desired feature request.

I just configured my Eero system, and found about this egregious limitation for such a premium product. I have a home server which requires me to use port forwarding.

My Apple Time Capsule allowed me to access my home server from either inside of outside my home network using my public IP address. I suspect it has to do with the "default host" setting.

And now I'm at a loss, not really knowing if I should return my new Eero system and look elsewhere for another WiFi system that does support NAT loopback.

Jeff C.  it would be great if you could weigh in on whether or not this feature in planned to be implemented in the near future. Is this even in the roadmap?

JoeKun I really can't believe they have not fixed this yet with all the backlash. Instead, they make their app look prettier.

We're all advanced users, which I think may go unrealized. I know the "target" customer is novice and selecting "simple," but that is NOT who is buying the product. 

Since it doesn't seem that this is on Eero's immediate timeline to resolve and I was within my return policy, I was forced to return the product and purchase one from a competitor that does support it.