Hey @dlakelan! I'm a couple years behind you, but I'm finally getting around to implementing a similar configuration for my HA OpenWrt setup. One question I didn't see pop up in this thread was around the WAN IP itself. Did/do you have a static WAN IP or were you able to implement your solution with a DHCP WAN IP?
Hey @_FailSafe I'm in the process of trying to get this back up and running by using a VM as the fail over. Then I can take my RPI out of service and either upgrade it or just have two VMs. The RPi has been doing routing duty continuously since 2020.
I have the WAN connection spoof a single MAC and it just gets the same IP when it brings up the WAN interface. Also the same ipv6 prefix. It basically doesn't have a static IP but the leases must be pretty long lived, at least hours if not days.
Thanks for the reply! This sounds like exactly my situation as well. From what I understand, while my ATT fiber connection is technically "DHCP", the optical port to which my premises connects keeps the same IP "forever". Not sure how exactly all that works in the fiber world, but I've had the same IP for years.
I'm going to give this a shot today and see how it goes. Fingers crossed! 
So do you have your WAN connection configured in keepalived with a VIP and then some static route(s)? Or something else?
I have VIPs set up for each of my VLANs and those are working now. Just struggling to figure out how to handle the WAN side of it.
Been a while since I had this actually working. But when I look at my scripts, it keeps the wan VLAN off until it gets the notification to become master, then it does ip link set up wan basically and runs dhclient on the wan.
when it gets notified to become standby it just ip link set down wan
1 Like