Routing in which routing decisions are dictated by administrative policy.
(a) Load balancing. (b) Failover.
Traffic between local interfaces will be routed through the original WAN interface and will never reach the gateway group; pfSense’s default behavior is to route external traffic to the primary WAN interface.
You are configuring an OPT_WAN interface and the OPT_WAN’s DNS server is not the same as the Monitor IP. We do not have to configure a static route for the primary WAN interface because external traffic is routed to it by default, and we do not have to configure a static route if the OPT_WAN’s DNS server is the same as the Monitor IP because pfSense will add a static route for the Monitor IP.
One for each OPT_WAN interface (and one for each 1:1 NAT mapping, if we have any).
Use Sticky Connections.
Acceptable answers: The load balancing gateway group isn’t working properly; the web page is cached and therefore isn’t refreshing when we reload it; the connections are weighted such that the secondary connection handles very little traffic; Use Sticky Connections or some other persistent connection option is enabled; other users are on the network and generating a share of the connections going to the nonprimary connections.
