Hairpin nat broken not working properly

[lleachii]

Ummmmm...isn't "Hairpin NAT" an analogous term for the OpenWrt term "NAT Loopback"???

Can't reach public IP from within LAN

"NAT loopback" as I've experienced it in OpenWrt - only works on the single IP/net in question. As other options, you'd have to: make a firewall redirect rule that covers the zone/interface/subnet; or DNS entry giving and A Record to the LAN IP For firewall config, I make a rule that allows the traffic and places the packet in the SRC network . This changes the DST IP from the Public to the LAN, and allows the packet to travel using the zones regular routing rules.

@lenovomi

they says hairpin nat has to be enabled; so i did it by unticking Rebind protection.

Still i cant access my hass using domain name within the local network even it works from hosts outside my network.

Using this firewall rule as an e.g. - it allows access to an HTTP server using its public IP or global hostname (which should resolve to its Public IP) from LAN:

@lleachii

config redirect                                          
        option target 'DNAT'                                         
        option src 'wan'                                           
        option proto 'tcp'                
        option src_dport '80'                                        
        option dest_port '80'                                      
        option src_ip '192.168.1.0/24'    
        option dest 'lan'                                            
        option dest_ip '192.168.xxx.yyy'                              
        option name 'REDIRECT_HTTP_LAN'

Rebind protection means someone setup a LAN IP in the global DNS...that may be likely; but usually NOT the case - because this can cause security issues if not really needed.

The most common use case would probably be for routers connected to networks with Private IP address and internal DNS servers giving out Private IPs of Private servers (i.e. no Public Internet).