Accessing Port Forwards from Local Networks
-
Hello All,
With TNSR on my 6100 I am having trouble Accessing Port Forwards from Local Networks.
Does anybody know the configuration which should be applied?In pFsense it was quite easy to configure using the documentation:
https://docs.netgate.com/pfsense/en/latest/recipes/port-forwards-from-local-networks.html
But in TNSR I dont know where I should start to be honest, any help would be appreciated :)
Attached is my conf.
-
@matlear according to the release notes for the latest version, known issue:
Unable to establish NAT hairpin connection [8014]
-
@matlear never been a fan of nat reflection, what is the scenario that you have/want to use it - can you not just use split dns setup to resolve your local resources to their local IP vs the public one?
This a better solution to be honest.
The only scenario that I see where nat reflection is only way is when the local client is forced to use external dns, say hard coded iot device or something - and for some reason this can not be redirected. Or the IP is hard coded into the client.. All of which are bad scenarios to have to work through.
I find that quite often nat reflection just seems to be solution that the user is familiar with - vs just locally resolve some fqdn to the local IP in the first place.
-
@johnpoz Actually quite a few of the proprietary VM's I run in my Lab depend on hairpin NAT to function correctly.
Cisco Expressways - Poly DMA Edge - Audiocodes & Ribbon Session border controllers.
Lack of hairpinning can be worked around but takes more effort :)
Split DNS I agree is easier for domain name look up but some of the advance SIP signaling I use routes back in through the wan IP address.