pfSense

Hello,
as it happened for the "Outbound NAT", there's the possibility that the CARP traffic can be matched by one of the rules in the "Floating Rules" (For example: Interface: LAN, source: ANY). This brings, under heavy traffic, to loose some of the CARP packets, which causes CARP to promote the secondary machine as master.

What could be done is to create a static rule just after the "floating rules" that matches all the CARP traffic and removes the queue (but I don't know if it's possible).