… For both LANs they my rules are directing to the gateway 'default'.  I have experimented with putting my loadbalance pools as the gateway but I have not been able to get it working.

This has to be the pool, otherwise it points the clients to one gateway only. And if that fails…

In your posted config I saw rules originating on OPT1 to access gateway "Wan2 Failvoer..." and "Wan1 Failvoer..."
I haven't seen those for LAN.

To get it working you should start with a card blanc rule  <allow* from*="" to*="" gateway:pool="">  on both your LAN IFs.

I haven't setup a dual WAN config myself yet. These assumptions are from my understanding of how it should work...</allow*>

Could someone please post or PM me their sanitized config if they are running in a Failover setup (not load balanced)??

Did you do this traceroute test from pfSense itself?
When WAN1 is down: are you able to ping the gateway of WAN2 from pfSense itself?

pfSense does not use the balancing pool for traffic origination on itself.
–> That's why you need static routes if you want to force some traffic to the second WAN (like DNS-queries).

I tried from a laptop connected to the network, not pfsense itself.  I completely forgot to try to ping WAN2's gateway, simply an external IP.

pfSense does not use the balancing pool for traffic origination on itself.
–> That's why you need static routes if you want to force some traffic to the second WAN (like DNS-queries).

Sorry a typo.
I meant: Currently it seems you push per DHCP the DNS-servers 208.180.42.100 and 208.180.42.68 directly to the clients.
–> The clients access the DNS-server directly.

Just delete the DNS-server fields on the DHCP-server config.
--> Clients will use pfSense as their DNS-server

If you add the static route for the DNS-server on pfSense, pfSense will be able to resolve names even if one WAN is down.
If you modify the config.xlm manually you can also add a tertiary and a quaternary DNS server --> 2 for each WAN. --> 2 static routes pointing to the second WAN.

Ah, thanks for clarification.
Concerning "Would this help as I was not able to even ping or perform a traceroute when I took down WAN1?".  What I meant to say is would this help as can not ping or traceroute an external IP address (with DNS out of the loop)?

Just delete the DNS-server fields on the DHCP-server config.
--> Clients will use pfSense as their DNS-server

If you add the static route for the DNS-server on pfSense, pfSense will be able to resolve names even if one WAN is down.
If you modify the config.xlm manually you can also add a tertiary and a quaternary DNS server --> 2 for each WAN. --> 2 static routes pointing to the second WAN.

As far as i can see from your config your DHCP clients use the DHCP directly.
1: Remove this and let the pfSense DNS-forwarder be the DNS-server for your clients.
2: Add a static route for one of your DNS-server entries on pfSense to the second WAN so pfSense is still able to resolve names when the primary WAN goes down.

1. If you mean that pfSense is acting as the DHCP server then yes it is.  Or are you talking about my ISP dhcp?
2. I will make this change.
Would this help as I was not able to even ping or perform a traceroute when I took down WAN1?

Could you describe what your actual problem is?
As in: what do you want and how does it differ from what you have.

The issue is that while the Load Balance pools are working, I am unable to reach the Internet when it fails to WAN2.  I believe this is due to my firewall rules, but am not sure.