Your NAT rules should not apply NAT to traffic originating from the firewall itself. (e.g. you do NOT want a source of "any" on NAT rules, but the LAN subnet or an alias of your internal subnets)

Found the answer –> http://forum.pfsense.org/index.php/topic,66838.0.html

Well, the solution is the same :) You do SNAT to virtual IP. Create alias with the virtual IP, then do Outbound NAT: IF Source is your WAN_IP THEN Translate address to VIP_ALIAS

It's not possible to utilize both CARP nodes at the same time for outbound traffic from the same internal systems. If your drops were done using LACP to a switch on WAN doing LACP, rather than direct to your individual nodes, it may work, but without two stackable switches there you'd lose some redundancy.

@doktornotor: So you basically broke a working sensible setup to replace it with this horrible kludge? Uh. Either undo the harm you did, or stick everything on one subnet. I undid the harm by removing the Virtual IPs, and I did set the IP addresses for each interface since the Virtual IP routine didn't have enough options. So this pretty much solved the problem. Thanks.

What about your firewall rules on the lan interface ? Have a look at this post: http://forum.pfsense.org/index.php/topic,63309.0.html

@KurianOfBorg: Definitely sounds like the routing. An IP alias is just like adding an additional IP on your PC. By default, everything binds to it. There were no routes added manually to the system, so it has to be something with Racoon/ipsec and the way it "takes over" in a sense.

It's exactly the same as it was before, just with a more appropriate name and location. The config options and settings are all the same, the only difference is where the page is located and its name.

how about using 1 pfsense only (without all the CARP things)…...can 1 pfsense ping all the public ip ...?? if not, ISP problem, if yes, your pfsense CARP setup problem.

just try to help… 1. First, make sure on single pfsense server, you can go out to internet.... enable automatic nat, removed all the static nat entries configure you pc gateway point to 192.168.1.252 make sure your pfsense WAN have default gateway point to the router (i noticed your wan gateway is in different subnet ???) Make sure step 1 is successful before proceed to step 2 2. repeat the above for the second pfsense server and point your pc gateway to 192.168.1.253 3. Configure CARP... make pfsense server 1 Master on both LAN & WAN point your PC gateway to 192.168.1.254...it should work...

Actually it depends on your setup…..automatic load balance not possible....but you can do manual redirect traffic to different pfsense server based on CARP priority on multiple VLANs setup.

@jimp: No, but that's not pfSense's fault, it's VMware. You can make a port group just for the ports of the firewall, and make that promiscuous, and then have another different port group for the clients that is not promiscuous. Thankx, works great.

@jflsakfja: I stand corrected on the backup sync settings then. If syncing certificates, wouldn't this also affect the webgui cert? (hostname on backup system is different than the master) Yes but that is easily solved by either using the same GUI cert for both, or by importing the cert from the secondary to the master before setting up the sync. Then re-select the correct GUI cert after the sync.

Thank you very much. I will try changing this options and tell you how it work.

If the CARP VIP is on the lagg interface, the link status of the lagg and thus CARP VIP should only flip if both NICs die.

If you have a Layer 3 switch, or any switch that supports VLAN and 802.1Q you can create additional LAN networks that can be individual /24's. I wouldn't suggest using a LAN block larger than a /24 as you can run into performance/stability issues with broadcasts overwhelming all hosts on the network. Instead, carve up that /22 into multiple blocks like so: 192.168.0.0/22: 192.168.0.0/24 - 192.168.0.1-254 192.168.1.0/24 - 192.168.1.1-254 192.168.2.0/24 - 192.168.2.1-254 192.168.3.0/24 - 192.168.3.1-254 This will also give you the ability to segment your network, and will make overall management easier. You can even split those /24 blocks into smaller network blocks so you can keep servers, management IP's, VIP's, VPN users, etc.. separate and firewalled across LAN's. For example, with the blocks above, we want to further segment the first block. First split them into two /25's: 192.168.0.0/24: 192.168.0.0/25 - 192.168.0.1-126 192.168.0.128/25 - 192.168.0.129-254 Then we can split the second block into two smaller, /26 blocks: 192.168.0.128/26 - 192.168.0.129-190 192.168.0.192/26 - 192.168.0.193-254 Yes you 'lose' a few IP's in each network for subnet, broadcast, and gateway IP's, but overall it's a great solution to optimally use your IP blocks. Hope this helps!

There's three ways to do this: 1. Create a 1:1 NAT which maps External IP 1 to Internal VM IP 1, and so on. Your VM's would have LAN addresses assigned to them and would sit behind the firewall. 2. Create a bridge connection between ISP and your XS farm. You will need an additional interface, VLAN or physical, and would have to place the internal bridge interface on your XS host/vlan. This isn't an optimal configuration so I wouldn't recommend it. 3. Ask the ISP to route traffic for your IP block to you via a transit link (preferably a private address subnet /29 or /30) and use your pfsense box to route traffic for your networks. You can create an internal LAN net, and a DMZ network as physical or VLAN interfaces (although I would recommend separate interfaces).

Hi, how about checking the switch where the pfsense connected and lastly the LAN card. If it's still the same after isolation above, try other motherboard. Hope this can help you. Thanks