New To Port Forwarding

heirkeyso

I tried to configure a port forwarding. On the attached file is my configuration. But when I tried to access it, the webgui of pfsense is the one opening. I need to open the PC with ip address of 192.168.0.18.

Your assistance is greatly appreciated.

Thank you in advance.

PortForwarding.jpg_thumb

doktornotor

Are you "testing" from LAN?

KOM

https://doc.pfsense.org/index.php/Why_can't_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

somertech

I am also having issues with NAT Reflection pfs 2.2.5.

I have multiple internal webservers on my LAN, and my port forwarding rules work from the WAN side. However, as the OP experienced, attempts to reach an internally hosted website at www.mydomain.com are redirected to an ssl interface which appears to be the PFsense webgui.

I read the suggested Wiki document and attempted to configure the Split DNS method as documented, but it didn't work for me. Attempts to reach internally hosted sites at www.mydomain.com no longer resulted in redirects to SSL, they simply didn't resolve at all.

So I then tried using the NAT Reflection option as documented and internal resolution works great, but then I could no longer resolve external addresses from LAN hosts. As a matter of fact all external addresses such as Amazon.com resolve to my internal servers. Obviously undesirable.

I'm not sure what I'm missing as I think I followed the guides as close to the letter as made sense for my setup.
If there are specific firewall rules needed to accompany Split DNS and/or NAT Reflection setup, it would be nice if the wiki included examples.

Any suggestions would be greatly appreciated.

Derelict

Don't just refer to some nebulous document without a link. Tell us what settings you have in the DNS Resolver.

Also of importance is that the only DNS server defined in the LAN clients is pfSense.

And you should start another thread. "New to port forwarding" doesn't describe your issue at all.

KOM

…attempted to configure the Split DNS method as documented, but it didn't work for me.

I'm sure we can get it working. As Derelict said, start a new thread and post all the relevant details you can regarding your DNS configuration as well as the client DNS settings you're testing from.