I am seeing a similar problem on pfSense+ 24.11 (patches applied).

The ADMIN group being REMOVED from user rights assignments on secondary/backup HA cluster members any time the password is changed on the primary member.

I am having to logon to the secondary members and manually add the user(s) back to the ADMIN group.

This is not desired behavior, and I confirmed it is not happening on CE 2.7.2 (patches applied).

@mike_vc

I used to have this issue too, so on every new firewall I setup, I always make sure to add the following values under System, Advanced, System Tunables:

net.inet.carp.preempt 1
net.inet.carp.ifdown_demotion_factor 240

Also, make sure that the primary firewall's CARP skew is 0, and the backup firewall's CARP skew is 100.

@michmoor Ok i know the problem. OPT interfaces are mismatched. I don't know how to align the OPT interfaces so the master and backup are in sync.

@CreationGuy
That's not a problem. However, you have to configure a separate backend for this. Then you can configure a frontend rule to forward certain traffic to it.

Actually you have all three services within a single backend pool, all in active mode. Hence you cannot determine which per rule.
HAproxy can only load balance between these backens this way.

I got it working after creating a new server to replace the one serving butiktrip.2nd

@viragomann
Hi viragomann,

thank you very much for your time and investigation. Your answer was very important bringing me back to the correct path for debugging. The reason, why clients can't reach the internet was an inconsistent configuration of pfBlockNG between the two HA members. I've ignored erros like this:

/rc.filter_configure_sync: New alert found: Unresolvable source alias 'pfB_BinaryDefense_v4' for rule 'NAT Allow HTTPS_2_xxxxxxxx'
Dec 14 16:17:17 svrfw02 php-fpm[32037]: /rc.filter_configure_sync: New alert found: Unresolvable source alias 'pfB_DNSBLIP_v4' for rule 'NAT Allow HTTP_2_xxxxxxxx'
Dec 14 16:17:17 svrfw02 php-fpm[32037]: /rc.filter_configure_sync: New alert found: Unresolvable source alias 'pfB_DNSBLIP_v4' for rule 'NAT Allow HTTPS_2_xxxxxxxx'
Dec 14 16:17:18 svrfw02 php-fpm[32037]: /rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:299: syntax error - The line in question reads [299]: rdr on lagg1.808 inet proto tcp from ! to 83.x.x.54 port 443 -> $SERVER_xxxxxxxx

After fixing this, switching between carps members works correctly.
Again, thank you for your assistance !!!!!

@kiokoman

After years, new internet provider, same problem, we have managed to switch our rack hosted servert to ha, and the same config worked perfect on the other isp network. So the problem is related to the internet provider, but saddly they say everything is ok...But its workes, so the config is okay, just need a good isp endpoint :D

@SteveITS said in WAN Gateway on Backup server in CARP shows down:

https://docs.netgate.com/pfsense/en/latest/recipes/high-availability.html#wan-addressing

Hi @SteveITS
Thanks for the prompt response. I have assinged uniqe ips on wan port of each pfsense box . and uniquie ip on lan of both pfsense.

yet when a pfsense box is in Backup mode i cannot get to wan from it. all pings form it fails. eve cannot get a ping replies when i ping the wan ip of another pfsens which has wide open rule on that interface,

Solution:

I connected the two PFS with a virtual Switch (VXLAN+IPSEC). For this i had to lower the MTU to 1360. Unfortunatelly the Adapter in PFSense was set to 1500 and not appling for the new MTU.

Setting down the MTU (in my case to 1360) manually in the SYNC-Interface-Options solved the problem.

@Snailkhan Have never seen that. Only one is Master?

You’re NATting to the shared LAN IP? What is that for?

@Snailkhan
Ensure that all interface pairs can communicate with the respective other node.

@Snailkhan
By default the primary interface IP is used for communication with other devices.

If you want pfSense to use the CARP VIP you have to add an outbound NAT rule to LAN or the respective interface and set the CARP VIP as translation address.

However, don't do this for any traffic! It would lead into issues with services running on both nodes, e.g. DHCP.
So limit the destination (IP and port) to the domain controller or whatever you need it for.

@SteveITS I would prefer not to add more gear for now, since this is temporary until I have two pfSense units and CARP. Maybe I'll just have both connected, but configure the 2nd one in case of longer downtime then.