I can successfully configure my home firewall to allow port forwarding BUT it won’t hairpin. This means that when I’m on my internal network I need to change from using the public IP address to the internal IP address of the home assistant server.
Could the app be updated to allow an “internal” and “external” IP address or FQDN instead of me having to re-configured the app each time I’m in/out of my network?
1 Like
It can’t do that just yet. There’s a feature request to support multiple instances, but it’s on hold.
What you can do is configure your firewall to do source natting and this will overcome the problem you are facing.
I use my local dns server to redirect the external dns entry to my local ha server’s ip to overcome this. Works great.
Can’t true NAT fix this?
I’m very familiar with building NAT rules in my firewall. Alas, the issue is that it won’t hairpin. That means that when I’m on the “inside” and attempt to access the Public (aka “outside”) IP address of the firewall it won’t redirect me to the NAT’ted “inside” address. If I’m on the “outside” it’ll work fine.
What I’m looking for is a “dual IP” setting for a single HA instance. I haven’t played with it but I did see a screenshot of an OpenHAB app that had 2 entries for adding IP addressing to connect to server. One was labeled something like “Public IP” and the other was labeled like “Private IP”.
1 Like