"
I was having a similar problem with a dual WAN HA configuration running 26.1.7, but it only seemed to affect the secondary firewall. I couldn't connect to the Wireguard VPN on the secondary firewall via the non-default WAN2. I think my default WAN1's ISP blocked the response packets as I never received them. After reading through this thread I set the Reply-To to the WAN2's gateway on the rule on the WAN2's interface allowing the incoming Wireguard traffic and it started working. After configuring the similar settings for the WAN1 wireguard rule I'm now able to connect to either firewall's wireguard on either WAN.
Jon
Jon
