Did you create firewallrules to allow the incoming traffic? Only 1:1 NAT is not automatically passing all traffic (which would be a bad idea anyway).
Let's say one of your IPs is a webserver for example you need a pass rule like this:
source IP any
destination IP <lan-ip of="" mailserver="">(NAT comes first, then firewallrules are applied so you have to use the internal IP as destination)
destinationport http (80)</lan-ip>
Ok here's the deal and it's got me very confused (By the way great job on this PFsense team so far this is great).
LAN IP 220.127.116.11 with DCHP enabled
WAN 18.104.22.168 / 8
wan gateway 22.214.171.124
now from internally I can view and ping most sites. But There are a few I can't like. stumbleupon.com (126.96.36.199) and suvault.com (188.8.131.52)
I know this is an issue with pfsense or the way I have it set up because when I plug in the old linksys with the same wan ip and lan ip it goes to these sites just fine and I can ping them. Anyone have any clue why this is going on?????
This looks like a Comcast business connection. I guarantee that WAN is supposed to be /29. I'm in the same 184.108.40.206/8 CIDR block (on two seperate connections) and /8 is NOT the correct netmask for machines attached to it.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.