I highly doubt the built-in load balancer (relayd) is going to adequately handle a handoff with Exchange. You should install the haproxy package and use that instead.

I finally found the solution YaY On Cisco ME3400E the default port-type is UNI and it has to be set to NNI. From official Cisco config guide: Traffic is not switched between these ports, and all arriving traffic at UNIs or ENIs must leave on NNIs to prevent a user from gaining access to another user's private network.

@f-meunier Seems better ! I'll let you know [EDIT] That works. Thanks for the help. Have a nice day

Hi Jimp. Thank you, that worked perfectly. Indeed i reverted from 2.4.4 to 2.4.3 and recovered the last configuration, which causes this version mismatch.

Is the primary node actually seeing the interface go down? That is what is necessary to trigger a failover. It will fail over just fine with an actual interface failure. Even only one of many. CARP does not protect against a failure at Layer 2. That is up to you to provide Layer 2 redundancy in addition to Layer 3. It has zero to do with NAT.

@derelict said in DHCP from Backup Node?: If you view Status > DHCP Leases you should see normal/normal on both nodes. If not, something is wrong. Yes, I got it working so far, and yes I gave both gateway and DNs the CARP Virtual IP. After figuring out I have to add the slave IP there it started working. Unfortunately only on two of the interfaces, but not on the third. There it says "My state: recover" and "Peer State: unknown state" This is obvious not "normal", but how do I troubleshoot? I alread stopped both services and removed the dhcp-leases files on both servers, but no change. I can ping both addresses vice-versa. How can I troubleshoot? After re-configuring the dhcp service again and again it went finally to "normal/normal". So it is working now and I am fine.

I personally really like the IP Alias VIPs stacked on the CARP VIP. You only have one "stream" of CARP heartbeats and you can move dozens of VIPs at a time from primary to secondary and back. The only time I generally make multiple CARP VIPs is for cleanliness in cases where you have VIPs in multiple subnets. I generally make one VIP per subnet and stack the IP Aliases that are also in that subnet on that VIP. This is a personal preference. If you make all of them CARP, then you need a VHID for each of them and any missed advertisement will result in that VIP swinging to the other node while the rest remain. This is never what you want. The stacked IP Alias technique reduces the advertisement traffic to that of just the one VIP.

What you possibly can do: Make 2 VPN tunnel. On from the first pfsense and one from the second pfsense. Then you can still make CARP but you configure to NOT sync the IPSec conig. When the failover takes place, the vpn tunnel will already be up. depending on your setup you may run ospf or another routing protocoll with the two vpn tunnel to make changes that are nessessary due to topology change. Best Regars, blex

Hi, thanks for reply. No, it's a dedicated interface and there is no captive portal in it. It's on a different Interface and also VLAN.

If you bring up the master again the slaves config will be overwritten by the master. To avoid that disconnect the masters sync interface and reverse the config sync direction by removing the "Synchronize Config to IP" from the master in System > High Avail. Sync and configuring the XMLRPC Sync on the slave. Ensure that all options you want to sync are checked.

It might work fine using an interface address or an IP Alias VIP but not work CARP (using the identical IP address) because of improper handling of the necessary MAC address behavior by something upstream.

I found that the solution can also lie in the interface settings. https://forum.pfsense.org/index.php?topic=129871.0 In the OpenVPN Client Protocol dropdown, you probably have selected "UDP IPv4 and Ipv6 on all interfaces (multihome)". That ignores the selected interface. Select "UDP on IPv4 only" This fixed the problem on my end.

I'm doing well this week with answering my own posts… Got this working by creating the IP Alias on the cache interface, then setting up outbound NAT for "This Router" as the source to the

Yes. preferably a /29

That was it, thanks.

Hi Derelict I found out that in hyper-v i must activate the option for "mac address spoofing" on the vNics, after that all works fine :) [image: Spoofing.PNG] [image: Spoofing.PNG_thumb]

Not that I know of.