GL.iNet Flint 2 (GL-MT6000) – MWAN3 Dual WAN Load Balancing Configuration Guide

GL.iNet Flint 2 (GL-MT6000) – Dual WAN Load Balancing Configuration

Hardware

  • Router: GL.iNet Flint 2 (GL-MT6000)

  • Firmware version: 4.8.3

  • OpenWrt-based firmware

  • Installed package:

luci-app-mwan3

Network topology

ISP1 → WAN port

ISP2 → LAN1 port (secondwan)

MWAN3 interface configuration

WAN

  • Enabled: Yes

  • Initial state: Online

  • Internet protocol: IPv4

  • Tracking method: Ping

Tracking addresses:

1.1.1.1

8.8.8.8

208.67.222.222

208.67.220.220

Parameters:

Tracking reliability: 1

Ping count: 1

Ping size: 56

Max TTL: 60

Ping timeout: 2

Ping interval: 3

Failure interval: 3

Recovery interval: 5

Interface down: 3

Interface up: 5

Metric: 1

SECONDWAN

Use exactly the same settings.

The only difference is:

Metric: 2

Members

wan_only

Interface: wan

Metric: 1

Weight: 5

secondwan_only

Interface: secondwan

Metric: 1

Weight: 3

Policies

default_policy

Members:

- wan_only

- secondwan_only

Last resort:

default (use main routing table)

isp1_policy

Members:

- wan_only

Last resort:

default (use main routing table)

isp2_policy

Members:

- secondwan_only

Last resort:

default (use main routing table)

Rules

Devices can be assigned to a specific ISP according to their IP address.

Example 1

Name: Smart TV

Source address: 10.1.1.10/32

Protocol: All

Sticky: No

Policy assigned: isp1_policy

Example 2

Name: Security camera

Source address: 10.1.1.16/32

Protocol: All

Sticky: No

Policy assigned: isp2_policy

Unassigned devices

Any device that does not have a specific rule automatically uses:

default_policy

Performance results

ISP1

Download: 500 Mbps

Upload: 30 Mbps

ISP2

Download: 300 Mbps

Upload: 300 Mbps

Both ISPs active

Download: 800 Mbps

Upload: 350 Mbps

Notes

This configuration provides:

  • load balancing;

  • automatic failover;

  • traffic separation;

  • continuous link monitoring;

  • device-based routing policies.

This setup uses MWAN3 load balancing and is not based on bonding technologies such as MPTCP, MLPPP, Speedify, or OpenMPTCProuter.

1 Like