
Egress Hairpinning
I run a couple servers inside my network, mostly relying on a reverse-proxy to accept connections on TCP 443 and proxy the connections to the right internal server. I don't run separate internal v. external DNS. Instead, I have a more typical setup where I define an external DNS server in eero, then the eero includes its address as the DNS server in all DHCP addresses, and forwards the requests.
As a result, though, I can't access my server by [subdomain].[domain].com while *inside* my eero network. I have to instead use DNS shortnames. This is annoying for a number of reasons.
-
Amazon has the AmpliFi HD on sale: https://goo.gl/2A1Rrz
Here is the UAP-Pro: https://goo.gl/DFPzVn
And Google WiFi is on sale too!!!!: https://goo.gl/uji3Yf
I have not heard the best stuff about the Orbi, though performance wise, it seems to be solid.
-
Just came back to say that the wait for hairpinning has become too much for me, and I ended up replacing my eero system with something that cost less and gives me not only hairpinning, DMZ, and QoS, but also gives me better coverage and throughput than eero did. I'll be resetting my eero units and selling them off to someone else who demands far less from their wireless router.
-
Hi everyone —
First and foremost, I'd like to thank all here for contributing to this topic and sharing your thoughts with us regarding your interest in Hairpin NAT. I'm excited to share that with eeroOS 3.3, Hairpin NAT is now officially supported on eero networks.
To use Hairpin NAT, all you will need to do is create a port forward. Once done, you will be able to access your devices from both in and out of your network.
If you are unsure what version your eero network is on, you can check by:
- Opening the app.
- Tapping the menu button.
- Tapping on Network Settings.
Under the section Network software, you will either see Update available (needs to be updated) or Up-to-date (your network is on 3.3).
Again, we greatly appreciate everyone's patience and understanding as we've worked on getting this feature out. As a company, we hold a high standard in any feature we implement, and it requires the necessary vetting to ensure that anything implemented both keeps your network secure and working as expected.
If you have any questions, please let us know.
-
Is it just me or has this been broken again with the latest software update? It has been working fine for me for months. But a couple nights ago, my eero network updated to 3.12.0 and now I'm getting an error when trying to access from inside my eero network. "Can't establish a secure connection to the server" error. Connections from outside the eero network are fine, it's only a problem with local connections.
This was all working perfectly until the eero software updated. Nothing else has changed.