49

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. 

161 replies

null
    • Chrisipedia
    • 6 yrs ago
    • Reported - view

    Set up new eeros and was sad to see this is not supported. +1 for this feature please.

    • CodeGrue
    • 6 yrs ago
    • Reported - view

    This is now supported in their latest firmware release, although I have not tried it yet to vouch for the quality. Odd they didn't post this here yet.

    • jalvani
    • 6 yrs ago
    • Reported - view

    👏🏽👏🏽

    • beiseman
    • 4 yrs ago
    • Reported - view

    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.

    • JoeKun
    • 4 yrs ago
    • Reported - view

    This is definitely not just you. This feature seems almost entirely broken with version 3.12.0. I just emailed eero support about it.

    • beiseman
    • 4 yrs ago
    • Reported - view

    I emailed them as well, but haven't heard back yet.

     

    I think I may have, at least temporarily, fixed it. I deleted my port forwards on the server in question and re-added them, and so far it seems to be better. Not sure if it will fix it permanently, so I'm hoping they register a fix anyway...

    • juampick
    • 4 yrs ago
    • Reported - view

    Hi! I'm having the same issue right now. After one of the last updates all of the DDNS port forwarding stopped to work. 

     

    I need an urgent solution to this.

      • txgunlover
      • 4 yrs ago
      • Reported - view

      juampick They're aware, the .1 was supposed to fix it, but hasn't completely.

      • juampick
      • 4 yrs ago
      • Reported - view

      txgunlover I installed 13.12.1 yesterday and it's still not working. I deleted all my port forwarding and re-add only 1 to test, and no-working. Any estimation? I also added a ticket without response.

      • txgunlover
      • 4 yrs ago
      • Reported - view

      juampick Yep, that's why I said it hasn't fixed it.  They're definitely aware though, and ask that you put the tickets in so they can continue to gather data.

    • tokyodude
    • 2 yrs ago
    • Reported - view

    Seems to be still broken. After reading a thread that’s 4 (!) years old about something as simple as hairpinning, I’m quite disappointed. I guess this is as good of a time as any to move to something else and upgrade to WiFi 6...

Login to reply

Content aside

  • Status Implemented
  • 49 Votes
  • 2 yrs agoLast active
  • 161Replies
  • 11208Views
  • 66 Following