A high availability Brume 3 setup?

Is it possible to set up multiple Brume 3s where if one fails, the backup Brume 3 will immediately activate to ensure the network stays active?

Hi, are you looking for an HSRP or VRRP setup for gateway redundancy, this type of active/backup gateway setup is typically implemented with VRRP, which lets two routers share a virtual gateway IP address. If the active Brume 3 fails, the backup device can take over that virtual IP so LAN clients can continue using the same default gateway.

Could you share your planned network topology, including how the WAN and LAN connections will be connected?

I'm looking for something similar to Ubiquiti’s Shadow Mode. I'm not sure what the technical term is for that high availability mode.

I'm still thinking about how to do this, and then I'll give you an idea of a topology. GL.iNet will sell more Brume 3 if this works as I want, as high an uptime as possible.

Hi,

Thank you for clarifying.

This type of design normally involves VRRP together with configuration and connection-state synchronization to minimize disruption during failover.

When you have finalized your proposed topology, you can share it with us.
We will review whether it is feasible and provide assistance where possible.

Thank you for your support and understanding.

So do GL.iNet devices even support VRRP? I did a quick search and I don't see anything about it.

My network topology will look like this. The goal is to have a backup Brume 3 ready to activate if the first Brume 3 goes down. Would this be easy to configure? I'm assuming the second Brume 3 will have identical settings to ensure a seamless transition?

Internet
|
Brume 3-- Brume 3
|
+-- LAN1 / Main network --> ASUS AP
| 192.168.8.0/24
|
+-- LAN2 / IoT network --> ISP AP
192.168.10.0/24

@charles2

Hi,
A similar active/backup gateway setup may be possible through manual OpenWrt configuration on Brume 3. You can refer to the OpenWrt high-availability guide, which uses keepalived for VRRP failover and conntrackd for firewall/NAT connection-state synchronization:

For redundancy, the two MT5000 devices would need to be connected in parallel to the same upstream network and to both LAN networks.
Connecting the second MT5000 behind the first one would not provide redundancy, because a failure of the first device would also disconnect the second device from the Internet.
A simplified topology would be:

Internet/Modem
    │
WAN-side switch or separate LAN ports on the ISP gateway
   ├── MT5000 A
   └── MT5000 B
      │
   LAN/VLAN switch
   ├── Main network → ASUS AP
   └── IoT network → ISP AP

Both devices would require coordinated network, DHCP, DNS, firewall and VPN settings, while using different management IP addresses and the same virtual gateway IP addresses.

1 Like

Can you please check your PM? It's a shame that you didn't check it before the weekend.

Hi,

Sorry for the delay. I’ve replied to your PM now.