High availability#
Network → High availability, at /ha. More than one way out is the Uplinks tab;
more than one router is VRRP and Connection sync. The old address /wan
redirects here.
| Tab | What it does | Documented on |
|---|---|---|
| Uplinks | Every interface with a default route: priorities, health checks, PPPoE, source NAT, load balancing and policy routing | Uplinks (multi-WAN) |
| VRRP | Virtual addresses shared with a partner router, and sync groups | VRRP |
| Connection sync | Open connections that survive a failover | Connection tracking sync |
Every setting on these tabs is edited on the page. In Advanced mode a fourth tab, CLI, shows all of it as the router's own commands — the block to start from when you build the second router of a pair, minus what must differ between the two: the VRRP priority and the addresses.
Deep links#
The tab is in the address, so a tab can be linked to and a reload keeps it:
/ha?tab=vrrp, /ha?tab=conntrack. The Uplinks tab is the default.
Every change here can cut you off#
These settings decide which way packets leave the router, and your session with the router is packets. The Commit Bar treats a change to uplinks, health checks, load balancing, policy routing, source NAT or VRRP as one that could cut you off: it offers Apply with auto-revert, which restarts the router with its saved configuration unless you confirm the change in time.
What the page does not do#
- Every health verdict is the router's own. The agent's own measurements are shown beside them, and the router acts on them only where a health check or a load-balancing test is set up. The page says which, per uplink.
- It does not touch the firewall. A second uplink needs the same input policy as the first; that is the Firewall page's job.
See also#
- Static routes — the routing table these mechanisms compete to write.
- Addressing — how an interface gets its address.