Bug #9284
closed
no default gateway after upgrade to 2.4.4_p2 using gateway group
0%
Description
Two pfSense boxes A and B using HA sync, A is master, B is backup.
Two gateways, Verizon (tier 1) and ATT (tier 2) configured for failover (member down).
System > Routing > Gateways > Default gateway IPv4 is set to the gateway group.
Post upgrade to 2.4.4_p2 when either box is restarted they do not have a default gateway. Previously (2.4.4) on rebooting boxes did have a default gateway (Verizon/tier 1 as expected).
ifconfig down to cause a gateway to go offline does not cause a failover or a default gateway to be set.
Workaround: In System > Routing > Gateways set Default gateway IPv4 to automatic (or one of the gateways) and save/apply. Can then set it back to the gateway group. Or route add default ${gateway}.
Updated by Art Manion almost 6 years ago
Art Manion wrote:
Workaround: In System > Routing > Gateways set Default gateway IPv4 to automatic (or one of the gateways) and save/apply. Can then set it back to the gateway group. Or route add default ${gateway}.
If a default gateway is set (automatic, Verizon, or ATT), pfSense will select the correct gateway according to tiers and member down behavior. For example: Reboot, set gateway to ATT (tier 2), wait, pfSense switches (correctly) to Verizon (tier 1).
Member down failover works otherwise as expected.
Updated by