The panel egress is injected as a routing rule, so a routing balancer is a valid target for it (unlike the geodata download, which dials a forced outbound tag and bypasses the router). Surface routing balancers in the panel outbound picker as a separate group, and emit balancerTag instead of outboundTag in the injected egress rule when the configured tag names a balancer, so the panel's own traffic load-balances across its members. |
||
|---|---|---|
| .. | ||
| config | ||
| database | ||
| logger | ||
| mtproto | ||
| sub | ||
| util | ||
| web | ||
| xray | ||