its a goog idea to use alias ip with /32 on both server? the routing goes every time to the active firewall. if not we must nat on the upstream firewall.

Hi, I have solved the problem! You must begin with the subnet addresses! e.g. xxx.yyy.99.128/25 128 is my network subnet address 255 is my broadcast address 129 is the gateway 130 have i configured for the WAN2 Interface address 130/25 When I go to Virtual IP add „other” select dropdown „network“ and type xxx.yyy.99.131 /25 then only the first IP 131 work! When I type  xxx.yyy.99.128 /25 all works so if it should :-) Regards Andreas

So nothing you are aware of actually goes 10gb?

You have configured FW1 to sync its states via the SYNC interface, using the the LAN IP Address of FW2..  Leave this field blank on BOTH firewalls.  Also, you'll need to make sure that you have a rule on SYNC that permits pfSync traffic from SYNC subnet to SYNC Address. On any interface(s) with CARP, ensure that you specify a rule that says 'permit carp from LAN subnet to LAN address'. On your LAN, you may also want to add a 'permit tcp from LAN subnet to LAN address on port 519' to ensure that the DHCP Fail-over communications are permitted through. Other than that, it looks correct.

@brian.stivala Your additional VIPs inside the WAN subnet or LAN subnet should be CARP VIPs in this case, NOT proxy ARP or IP alias. @dotdash: Only CARP VIPS are sync'd. Alias IP's are not. You should add all your VIPs as CARP. If you have additional routed subnets, you may need to add an alias IP on the secondary subnet on each box, then add the rest as CARP. Not quite that simple. Proxy ARP - Never Syncs CARP - Always Syncs Other type - Always Syncs IP alias bound to normal interface - Will not sync IP alias bound to a CARP VIP as its interface - Will sync IP alias bound to localhost (2.1+) - Will sync See here: http://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses%3F

This is solved, and where actually surpricingly easy. Added the VIP as static IP, next I created an NAT rule, where the source = the DMZ network, and the NAT address is = VIP. Voila, solved. :) Now ingoing traffic to both IPs is working, and client and dmz have different outgoing IP addresses. cooool  ;D

why not assign a static IP to the management interface of ESX so that you can always connect to ESX. then configure your pfsense to boot first in ESX, and add a startup delay on the other VMs so that when they boot pfsense is already up?

Thank-you, Jim.  That was the issue - I needed to tighten up my NAT rule.

@mrzaz: @vbman213: Fixed: http://redmine.pfsense.org/issues/3075 Thanks! I have just updated to the latest build (2.1-RC0 (i386) built on Tue Jul 9 23:03:10 EDT 2013" but still see this problem when trying to remove "IP Alias" entries. I get "This entry cannot be deleted because it is still referenced by at least one Gateway." when trying to remove one IP Alias.   (I only have one primary IP defined in the WAN-interface .51 at end and one VirtualIP "IP Alias"with .53 at the end. Is in same subnet as primary IP. The "IP Alias" was created in an earlier build from June. I was only doing some tests for a colleague and need to undefine the IP Alias as this IP is normally used in another router and is temporary disconnected so I could do the test. As long as this IP is now tied to pfSense it will answer ARPs and I will get an IP collision. Dan Lundqvist Stockholm, Sweden I would recommend posting on the issue page @ http://redmine.pfsense.org/issues/3075

Binding the Alias to localhost worked a treat.  I read that you shouldn't bind it to the WAN interfaces because it'll cause an IP conflict,  I also noticed that Aliases bound on those interfaces don't sync over XMLRPC.  However, an Alias bound to localhost synchronizes as expected. Thanks again for all your help.  This NAT/Other VIP stuff is much quicker to configure.

You can find the source of the net.link.ether.inet.carp_mac patch here: https://github.com/pfsense/pfsense-tools/blob/master/patches/RELENG_8_3/carp_correct_mac.diff As far as I understand, it only changes the MAC-Address of outgoing ARP-Pakets so it doesn't solve the problem. We managed to get around the problem by putting a linux box between the pfsense firewall and the router. It has no ip configuration but a bridge(like a hub) and rewrites the mac-addresses of the outgoing packets. The configuration looks something like this: brctl addbr br0 brctl addif br0 eth0 eth1 eth2 ifconfig eth0 up ifconfig eth1 up ifconfig eth2 up ifconfig br0 up ifconfig eth0 0.0.0.0 promisc ifconfig eth1 0.0.0.0 promisc ifconfig eth2 0.0.0.0 promisc ebtables -t nat -A POSTROUTING -p IPv4 --ip-src <ip3>-j snat --to-src 00:00:5e:00:01:2d ebtables -t nat -A POSTROUTING -p IPv4 --ip-src <ip4>-j snat --to-src 00:00:5e:00:01:2e</ip4></ip3>

lHmm.. I suddenly realized the ISP told me to be sure that the vrrp routers could see each other using my network. So if stp blocks one port, vrrp will no see the other router. It is btw a Dell 3348. Greetings, Roger

You cannot do both NAT and routing. I does not work unless you are NATting to LAN and routing a completely separate IP block to say DMZ. Your ISP must route that separate IP block to an IP on you WAN block. Otherwise you are going to have to work through whatever NAT problem you have. Perhaps using the SIPProxy package?

Complete failover to the backup machine is controlled by net.inet.carp.preemt = 1, which is the default for PFSense as far as I know (at least on our 2.0.1 production machines). So yes, should any CARP VIP lose link (or rather, should the backup machine stop receiving the heartbeat from the primary), the backup will bring up the VIPs on all interfaces. I'm not quite sure what you're asking here, but an initial setup to get you started with CARP is demonstrated here: http://doc.pfsense.org/index.php/Configuring_pfSense_Hardware_Redundancy_(CARP)