Accessing Port Forwards from Local Networks
-
@rahim
Have you tried the NAT Reflection method?You can enable NAT Reflection also in the NAT rule for 14000. Try out "pure NAT", if that doesn't work try "NAT + proxy".
-
@rahim said in Accessing Port Forwards from Local Networks:
Kaspersky I uses IP address for connectivity.
Why would you do that? Use a fqdn, so you don't have to touch every single machine if your public IP happens to change..
There are plenty of FREE dynamic dns options, if you don't actually own a domain. But at a loss to how a place of business doesn't have a $10 a year domain they could use.. There are plenty of free and not free services to do ddns with your own domain.
Or you can just set this fqdn to point to your IP statically.. Since how often does it change?
-
@viragomann Yes I try NAT Reflection method but not work well for me.
-
@johnpoz Thank you but their is problem with free DNS or paid DNS our IS team are not allowed us to do this because its compromise for system these type of free dns leaks the information which is not good for us thats why I try to resolve this issue by using pfsense.
-
What? You buy a domain lets call it domainX.tld - and you point that to your IP.. How does that compromise anything? The whois info to who owns that domain can be hidden.. It only points to an IP..
Every company on the planet has this info out there.. Who are you hiding from?
If you want to hit ip 1.2.3.4 which is your public IP while your internal, then nat reflection is how you do that.. If your saying its not working - then show us what you setup so we can help you figure out what your doing wrong.
Are you behind a double nat, if so nat reflection would have to be done at the box that has the wan IP on it, if that is in front of pfsense.
-
@johnpoz Thank you so much for your valuable suggestion NAT reflection works for me i use (NAT+Proxy) setting this option resolve my issue.
Thanks to all help me out @Rico @viragomann -
Glad you have it working now.
-Rico
-
If its working and your happy, then all is good.. But such a setup is not the "correct" way ;)
It makes no sense to send traffic to your wan IP, just to be hairpinned back to hit the IP sitting next to you on the lan..
Its like you want to go the dining room from the kitchen in your house - but hey lets go out the front door and back in to get there ;)
-
@johnpoz said in Accessing Port Forwards from Local Networks:
Its like you want to go the dining room from the kitchen in your house - but hey lets go out the front door and back in to get there ;)
Good point
-
And then hey when want to go back to the kitchen - back to the front door ;)
In the big picture prob doesn't matter all that much, unless your moving a lot of traffic. But it sure is not the "optimal" sort of setup..
Why would you want to do that?
