The only way you can support HA Active active in Peplink’s world is by using a routing protocol.
We do this at Venn with our global WARP infrastructure delivering public IP subnets to the LAN of Peplink devices in an active / active setup.
In this video we show how we’re doing that with a Juniper firewall as the client that recieves the public IPs. Venn WARP - HA Demo
The beauty of this is that it can be mismatched routers (in this case a B One 5G and a BR2 Pro).
Perfect if you happen to have a pair of B580X in a rack, or a pair of BR2 Pro’s in a remotely driven taxi for hardware resilience - especially since you can combine the bandwidth of all the active WAN links on both devices at the same time…
So in that demo only the juniper has the public IP’s, the connections to the 2 peplinks are /30’s rfc1918 addresses. The peplinks each advertise a default route to the juniper and the juniper advertises the public prefix to both of the peplinks, which then advertise back to the fusionhub which hosts the bigger public prefix.
You designate the primary peplink by using as-prepend on the secondary paths and use higher costs on the speedfusion tunnels.