Primary node is no longer routing to WAN but secondary works after upgrade
-
I have pfSense installed on two netgate devices in HA with CARP. A few days ago I upgraded from 2.4.3 to 2.4.4. On node2 (secondary), I upgraded the system and it upgraded without issues. Then I went to node1 (primary and working correctly) and entered persistent maintenance mode, and it appeared to upgrade correctly. Then I left persistent maintenance Mode on node1, and routing to the Internet stopped.
I entered Maintenance mode again on node1 and routing started working fine again. I checked gateways, and routing and logs and I haven't found any issues. I restarted the edge switch. I waited 5-10 minutes but nothing changed. Both nodes appear to be identically configured.
If I go to the Edge Switch, the ARP table has the CARP mac address of 00:00:5e:00:01:04 as expected. The VHID on both firewalls for the wan is set to 4. But when I am routing through node2, I can ping its VIP. But when I leave maintenance mode, and routing through node1, pinging the VIP no longer works. But I can ping the actual IP addresses of both nodes.
It looks like maybe the Layer2 mac address for the CARP isn't being set properly on node1? I tcpdumped the CARP interface on node1 while traffic was supposed to be routed through it and I did not see a match for 00:00:5e:00:01:04. But when I tcp dumped on the CARP interface on node2 while traffic was being routed through it, I saw a couple of matches for 00:00:5e:00:01:04.
I thought maybe something broke in the upgrade to 2.4.4, so I upgraded node1 to 2.4.5 and no behavior changed.
Any ideas? I've never had a problem with routing on node1 (or node2) before until after the upgrade from 2.4.3 to 2.4.4. Thanks