@ILO_EWS traffic comes into the wan - that is what is connected to the internet.. Then pfsense would port forwarded it to the IP you set to forward to on your dmz..
If the traffic never hits your wan, kind of hard to forward it to your IP in your dmz.
This an example of a port forward.. You should have a port forward rule
portforward.jpg
Which would by default create the firewall rule you need
wanrule.jpg
So the port forward says any tcp traffic on port 23040, send it to my plex server that is on 192.168.9.10 on port 32400
The firewall rule allows this.. The only difference really in mine is that I limit what IPs can be forwarded to IPs that are in my pfb_allowPFb alias, which is the IPs that check if plex is available, both from plex check, and my own checks to notify me if plex goes down. And your IP also has to be a listed US ip.. All of my users are in the US.
But traffic never hits my wan ip, pfsense could never forward this. You will notice have forwarded 6.22GB of traffic through this rule since the last time those counters were reset.
If when you do a packet capture on pfsense - and do say a test from that can you see me site and you never see anything hit pfsense wan interface how could it ever forward it?
here via a packet capture I can see on my wan traffic come in on port 23040, and in my case an answer back - but if that traffic never comes in on 23040 pfsense could never forwarded it to be answered.
trafffic.jpg
