Have you tried "enable carp failover" in the routing settings?
Now the missing piece is that you need a link - preferably dedicated high bandwidth - between the two boxes and run a BGP peering on that. This is called iBGP (internal). The only difference if a iBGP and an eBGP (external) peering is that in iBGP both peers use the same AS number.You can use the HA link for that, of course.Now in case one of the external peerings goes down, but packets still arrive at the box now without a proper uplink, it will know to forward the traffic to the peer.
Quote from: bimbar on September 28, 2024, 11:32:38 amHave you tried "enable carp failover" in the routing settings?I've looked at that setting and I don't think it does what I want it to do. The docs say that it will shutdown the BGP service when CARP is in backup, but that means that the failover will take a bit of time while BGP starts up on the other node and therefore result in a noticeable interruption. It's also unclear to me whether that setting will force CARP into backup mode if BGP is down.I'd rather an acitve-active setup for BGP and have it switchover with minimal interruption.I think there must be some way to configure BGP so traffic can be routed to the other node if one of the WAN or LAN interfaces is down/in backup.