If I'm reading your question right, go into the NAT rules and enable advanced outbound NAT.  At that point, use the internal range of IP addresses for the 15 users (for example 192.168.0.16/28) and NAT them to one of your static addresses (using Virtual IP's set up in firewall menu), and then put a rule at the end for "catchall" using the final IP. For example, if your network was 192.168.0.0/24 and you had public range x.x.x.1-x.x.x.5 x.x.x.1 is the WAN address of your firewall x.x.x.2-4 are the 1:1 NATed ip's to maybe 192.168.0.10, 11, and 12 to give 3 users Static IPs (if using DHCP, make sure to map those MACs to 10,11,12) x.x.x.5 would have an advanced outbound NAT set up as 192.168.0.16/28 for source (use DHCP leases to give to those clients in that range from 17-30) Make your last NAT rule the one that NATs 192.168.0.0/24 to "WAN Interface IP" and you should be fine. Let me know if you need more specifics.

Two logs fro the same timeframe would be perfect: one tcpdumpfrom pfSense another one from remote CP. On pfSense: tcpdump -ni <wan_interface_name>host</wan_interface_name>

Then go ahead! do dumps and post them here.

Upgrade in 1.2.3 RC3…. now it is ok... finally : not all ok...

You have the addresses swapped.  LAN addresses should be internal (private (10/8, 192.168./16 and 172./12)) and WAN addresses are either DHCP or what your ISP defined for you.

Issue was resolved by performing a clean re-install. Did not tyr to restore previous configuration file on new install.

Thanks, but it didnt help. But the problem is solved. I connect throu my LAN IP and my friends throu the WAN.

Sry was afk the last 2 days. Thx a lot it worked perfectly. ;D ;D

It just occured to me my last post wasn't clear. I need to forward RDP (3389) from different external IP's to different internal IP's. I tried setting up multiple rules after creating a single NAT rule, with different source IP's but it only hit on the first rule even if the source IP was not the same.

Are you using the FTP-helper? If yes: Disable the helper. You need to set up your FTP server to use a fixed passive port range and then forward this range additionally. What exactly do you mean that this is not port 21 specific? Do you see the exact same thing with logs on your webserver or whatever you're running on this machine? Are you source-NATing?

Ok - so I have a very similar problem to this but after applying your fix I still have no joy. My VoIP system is Microsoft OCS R2 and I can't get audio between an external client on the Internet and an internal client. PFSense should now be completely transparent but still I get no audio.

Thanks Drees, I put this system in production yesterday, and it seems like what you are saying is exactly correct.  I was just making sure there were going to be no surprises down the road, and since 1:1 and outbound are in different tabs, there was no way to "order" the rules to act like I wanted.

Problem solved in my ignorance I did not give the AP's a passthrough on the captive portal

Probably you just need to add outgoing NAT INTERFACE=WAN, SRC=10.1.1.0/24, SRC PORT=, DESTINATION PORT=, NAT ADDRESS=207.X.X.51, NAT PORT=*, STATIC PORT=NO

Well, port forwarding and websurfing seems ok now…except that the FTP forwarding causes problems. May the use of a load balancer affect the transfer stability ? My opinion is that DNS don't always resolve the same IP...

@GruensFroeschli: I dont think it's related, but: Are your VLANs all on the same switch? I see that you mix tagged and untagged traffic on the same interface. This "could" be a problem. Yes, they are. The interfaces on the pfsense box are in a vlan which is native on the trunk port on the switch. I dont think you can do with the current setup what you describe. Traffic would have to leave via one interface ( the /28), get NATed, reenter on the same interface and get routed to the WAN. Well, can I get "around" this by using another physical interface on the pfsense box for the PublicInternet, instead of using a vlan interface, and "moving" the rules to that interface ? If that would work, I'd (not really happily) do it. How does you ISP handle traffic on his side? Will traffic from your IPs be routed to your main WAN IP no matter where it comes from? My ISP routes all traffic to the /28 subnet via my public wan interface IP.  I assume that in their upstream router they have something like this: ip route A.B.C.192/28 0.0.0.15 D.E.F.21 and are exporting this route to BGP/OSPF/MPLS or whatever they speak upstream You could scrap the /28 VLAN and add the additional public IPs on the WAN directly with PARP type VIPs (CARP wont work since it's a different subnet). You then can use these VIPs in outbound NAT rules. I NEED the /28 VLAN; this is essentially where I can do "internet" testing directly, without having to make ruleset changes on the firewall. There's at least a half dozen boxes on that subnet now, and I do not really want to to make VIPS and manage  a constantly changing ruleset for each one of those boxes, some of which might be "foreign" machines with DHCP assigned addresses. If I can make this work by using a separate physical interface for the PublicInternet, I'd be happy, but have to forgo using CARP which I was "saving" the last interface for (its an ALIX)….