OK I understand now and my previous advice still applies.  It should be one NAT rule (port forward) to expose the server on VPN to WAN, and one firewall rule to allow the traffic to flow.  That's it.

No pfSense config required if I understand you.  The client on the same internal segment as pfSense NIC just needs to use the pfSense LAN IP address as its gateway.  I'm not sure how WAN being bridged or NATed makes any difference to the client on the LAN.

Pop over to this thread to continue the VPN discussion: https://forum.pfsense.org/index.php?topic=102977.0

I got FTP to work by setting the passive port range on the ftp server then opening those ports with a nat rule to 192.168.0.xx9 for the ports I opened. Seems to be working in chrome in IE I had to turn off passive mode on a remote client to make it work. That seems odd since it worked in chrome but not IE until I turned that off and my understanding that forces it to 20 -21 any way and those were already open.

You can enable NAT reflection in "System: Advanced: Firewall and NAT" or also per rule. There is no need to recreate rules. The rules added by NAT reflection are invisible.

@johnpoz: I do believe its even being removed in upcoming 2.3.. Already gone there.

Access it from where? Good list of things to check here: https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

And does pfsense have a public IP on its wan or private?  If your behind a double nat its going to be difficult to forward ports inbound to your ps4 or even have UPnP do it for you.

I have had problems with using that alias in the destination address field. Try changing it to the WAN IP address and retest.

OK you were right, the route wasn't setup correctly :(  Everything is working perfectly now.  Thanks a bunch for your help!

Thanks very much, I believe I have it working.  Routing is what I was looking to avoid, as you surmised!

https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

How are you routing traffic for those destinations to PIA? What are your firewall rules on the source interface? Outbound NAT rules only tell the firewall what translations to do if the interface is sending matching traffic. They don't route anything.

@aclaus225: I just installed my pfSense box and I am trying to set up port forwarding, but perhaps missed a step in my configuration. The IP address on my external port is .85 and if I set up a route in Port Forwarding that goes to .85 then it comes through fine.  I, however, want to set a port forward on .84 and when I follow the same pattern in Port Forwarding everything works.  However, I am not able to get to RDP through .84.  What additional configuration do I need to do so that .84 is reachable through pfSense? I can't tell if ".85" and ".84" are public or private IPs. You need to post more information on your setup and what you are trying to achieve.

@ismaelnoble: has anyone managed to get chained nat to work in PfSense, im looking to do something similar to proxy chaining where the setup would be something like WAN–>pfsense wan ip--->pfsense wanip2---> host on wan2 where i would type in pfsense wan ip: 8000 if would nat to wanip2 8000 at which point the system would then nat wanip2 8000 to host on wan2 port 80. i have the system setup to the point where i am able to type in wanip2 8000 and get the web port of the host on wan2 i also have the nat setup for wan1 port 8000 to wanip2 8000 but cant get it to work from the wan1 side. i have tested the forward from wan1 port 8000 to a lan host and it works so it may be a setting im missing to facilitate the chaining of wan rules. not sure about your question . can you draw your network topology ? if there are nat after nat affter nat .. going on and you want to forward a port for application at last nat translations..assign the host static ip and do it straigth from throughout the chain..

^ - Great. Now I'm going to have to get through the rest of the day without laughing out loud about this.

Really?