GL.iNet Flint 3 (BE9300) review
The GL.iNet Flint 3 is the Wi-Fi 7 successor to the Flint 2: a home router with five 2.5G Ethernet ports, a Qualcomm chipset, built-in VPN and GL.iNet's OpenWrt-based firmware.

GL.iNet Flint 3 (BE9300) review
The GL.iNet Flint 3 is the Wi-Fi 7 successor to the Flint 2: a home router with five 2.5G Ethernet ports, a Qualcomm chipset, built-in VPN and GL.iNet’s OpenWrt-based firmware.
Who is this for? Home users who want tri-band Wi-Fi 7 with built-in VPN and OpenWrt-based firmware. The Flint 2 is the more affordable Wi-Fi 6 choice if Wi-Fi 7 isn’t a requirement.
The Flint 3 is the home router successor to the Flint 2, and GL.iNet now also sells the costlier Flint 4 above it. Where the Flint 2 has Wi-Fi 6, the Flint 3 has Wi-Fi 7. Add five 2.5G Ethernet ports, a Qualcomm chipset and GL.iNet’s firmware, which is built on OpenWrt.
Specifications
| Property | Value |
|---|---|
| Processor | Qualcomm quad-core 1.5 GHz |
| RAM | 1 GB DDR4 |
| Storage | 8 GB eMMC |
| Wi-Fi | Wi-Fi 7 tri-band (BE9300) |
| Wi-Fi speeds | 688 Mbps (2.4G) + 2,882 Mbps (5G) + 5,765 Mbps (6G) |
| Ethernet | 5x 2.5 Gbps (3 LAN + 1 WAN/LAN + 1 WAN) |
| Operating System | GL.iNet firmware 4.10 based on OpenWrt 23.05 (Qualcomm SDK); no official OpenWrt yet |
| WireGuard | up to 680 Mbps (GL.iNet’s figure) |
| OpenVPN-DCO | up to 680 Mbps (GL.iNet’s figure) |
| Price | $209.99 / €213.52 |

Wi-Fi 7: what changes in practice?
Wi-Fi 7 brings three relevant improvements over Wi-Fi 6/6E:
Multi-Link Operation (MLO): A Wi-Fi 7 device can use several bands at once. On the Flint 3 this is a separate MLO network that you add under Wireless, with at least two bands; with 6 GHz in it, the security setting is WPA3-SAE.
4K-QAM: 4096-QAM packs more data into each signal than the 1024-QAM of Wi-Fi 6 and 6E.
Lower latency: GL.iNet names this as MLO’s benefit, which matters for gaming and video calls. It does not raise VPN throughput.
Practical note: Wi-Fi 7 requires Wi-Fi 7 clients (newer laptops and phones). Older devices connect fine via Wi-Fi 6 or 5.
Five 2.5G ports: the difference
The Flint 2 has two 2.5G ports (WAN + LAN) and four Gigabit LAN ports. The Flint 3 has five 2.5G ports: three fixed LAN ports, one configurable WAN/LAN port, and one WAN port. That means:
- Wired devices can reach up to 2.5 Gbps if your NAS, server or gaming PC supports it
- Backbone connection to a Wi-Fi access point or switch runs at 2.5G instead of 1G
- You can switch LAN 1 to a second WAN port for failover or load balancing

WireGuard: 680 Mbps
GL.iNet rates the Flint 3 at up to 680 Mbps over WireGuard. That is less than its figures for the Flint 2 (900 Mbps) and the Brume 3 (1,100 Mbps). GL.iNet doesn’t explain the gap, and we didn’t measure it.
If your internet connection is below about 680 Mbps, this figure isn’t your limit. If WireGuard speed is your top priority, look at the Brume 3 (no Wi-Fi), the Beryl 7 (a Wi-Fi 7 travel router, also rated 1,100 Mbps) or the Flint 2, all cheaper, or the Flint 4 (1.5 Gbps), which costs more.
Flint 3 vs Flint 3e
GL.iNet also sells the Flint 3e (GL-BE6500) — a cheaper Wi-Fi 7 sibling, not a successor. It keeps the Qualcomm chipset and the five 2.5G ports but drops the 6 GHz band (dual-band instead of tri-band) and uses 512 MB of NAND instead of 8 GB eMMC. If you want Wi-Fi 7 and 2.5G ports but have no 6 GHz-capable devices and don’t plan to run heavy OpenWrt packages, the 3e covers most of the same ground for less ($179.99 / €188.10). This review is about the tri-band Flint 3.
Qualcomm vs MediaTek: does it matter?
The Flint 2 uses a MediaTek chipset (Filogic 830). The Flint 3 uses Qualcomm (the IPQ5332, according to the community port below; GL.iNet itself only says “Qualcomm quad-core”).
For normal use: you won’t notice the difference. Both run GL.iNet’s own firmware, built on the chip maker’s development kit: OpenWrt 21.02 on the Flint 2, OpenWrt 23.05 on the Flint 3, according to their firmware images (4.11.0 and 4.10.1). The Flint 2 is a firmware version ahead right now, so some menus differ.
For official OpenWrt, the Flint 2 is ahead: official OpenWrt supports the Flint 2, so you can replace GL.iNet’s firmware with the project’s own. It does not support the Flint 3: its Qualcomm platform is not in OpenWrt yet, and the proposal to add it has been open since April 2026. An unofficial community port exists (openwrt-flint3 on GitHub) with Wi-Fi 7, LAN and WAN working, but its maintainer lists open stability problems under sustained load and warns that flashing it can brick the router. If running the project’s own OpenWrt matters to you, choose the Flint 2. Sources: OpenWrt source tree (main branch) and pull request #23161, the openwrt-flint3 README, read 7 November 2026.
Older OpenWrt base: firmware 4.10 builds on OpenWrt 23.05, which OpenWrt itself lists as End of Life since August 2025. GL.iNet says it patches security holes in older versions and publishes security advisories; we didn’t check which fixes it carries over, so keep the firmware up to date.
Built-in features
Via the GL.iNet web interface:
- WireGuard and OpenVPN client
- DNS-over-TLS and DNS-over-HTTPS
- AdGuard Home
- VPN policy per device and per domain
- Guest network, separated from your main network, with optional client isolation (AP Isolation)
- Kill switch
- Multi-WAN failover
Flint 2 or Flint 3?
| Flint 2 (GL-MT6000) | Flint 3 (GL-BE9300) | |
|---|---|---|
| Wi-Fi | Wi-Fi 6 dual-band | Wi-Fi 7 tri-band |
| Ethernet | 2x 2.5G + 4x GbE LAN | 5x 2.5G |
| WireGuard (GL.iNet) | up to 900 Mbps | up to 680 Mbps |
| Chipset | MediaTek | Qualcomm |
| Price | $169.99 / €166.75 | $209.99 / €213.52 |
Choose Flint 2 if: You want higher WireGuard speed at a lower price and Wi-Fi 6 is sufficient.
Choose Flint 3 if: You want Wi-Fi 7 or you have multiple 2.5G wired devices.
Caveats
Wi-Fi 7 is only meaningful if your clients can use it: Buying a Wi-Fi 7 router for a house full of Wi-Fi 5 and 6 devices is often a future-proofing decision, not an immediate upgrade. That is fine, but it should be understood as such.
It is not the best GL.iNet box for pure VPN throughput: If your main reason to buy is WireGuard performance, the Flint 3 is not the strongest value in the lineup. The Flint 2 and Brume 3 are the cheaper, more direct answers.
Price creep is real in this tier: Once you are paying for Wi-Fi 7 and full 2.5G port density, you need a network that will actually benefit. Otherwise the Flint 3 can easily become an expensive “nice on paper” purchase.
Pros and cons
Pros
- Wi-Fi 7 with Multi-Link Operation over the 2.4, 5 and 6 GHz bands
- Five 2.5G Ethernet ports, one of which can be a second WAN
- GL.iNet firmware on the newer OpenWrt 23.05 base (the Flint 2 is on 21.02)
- Full GL.iNet feature set: AdGuard Home, DNS-over-TLS, kill switch, multi-WAN failover, per-device VPN policy
- OpenVPN-DCO support, rated up to 680 Mbps like WireGuard
Cons
- WireGuard rating (680 Mbps) is lower than the Flint 2 (900 Mbps) and Brume 3 (1,100 Mbps)
- More expensive than the Flint 2 while offering less pure WireGuard throughput
- Wi-Fi 7 benefit is limited unless clients also support Wi-Fi 7
- No official OpenWrt support yet, only an unofficial community port; the Flint 2 has it
- Firmware on OpenWrt 23.05, End of Life upstream
Getting started
These steps assume a new or reset Flint 3 on firmware 4.10. Already set up? Start at step 2.
1. Installation
Connect the Flint 3 to your modem or ISP router via the WAN port. Connect a device to a LAN port with Ethernet, or to the Wi-Fi network printed on the router’s label. Open 192.168.8.1 in a browser, choose your language and set an admin password.
2. Setting up VPN
Go to VPN → VPN Client Profile, choose WireGuard, click Add Manually and upload the .conf file from your VPN provider. Then go to VPN → VPN Dashboard, click Add VPN Tunnel, select that configuration, and choose All Clients and All Targets. Check that Kill Switch is on in the tunnel’s options, then switch the tunnel on. Kill Switch blocks the tunnel’s traffic if the VPN drops; a tunnel you switch off yourself sends traffic over the normal connection. Test the connection with an IP check on a connected device.
3. Encrypted DNS
Go to Network → DNS. Under DNS Server Settings, set Mode to Encrypted DNS, pick a DNS Provider such as Quad9, set Encryption Type to DNS over TLS or DNS over HTTPS and click Apply. On this firmware, Allow Custom DNS to Override VPN DNS on the same page starts on: VPN traffic then uses this DNS instead of your VPN provider’s. Turn it off to keep your provider’s DNS. For devices with their own DNS server, turn on Override DNS Settings of All Clients; this only catches unencrypted DNS.
4. AdGuard Home
Go to Applications → AdGuard Home, switch it on and click Apply. It works as a local DNS ad blocker for all devices on your network, with no per-device installation. Once it is on, the DNS page says step 3’s settings no longer work. Its default upstream servers (8.8.8.8, 9.9.9.9) are unencrypted. Step 5 of the setup guide fixes that. Its own interface has no separate login: only a browser logged in to the router gets in (our reading of GL.iNet firmware 4.7.4 and 4.11 and AdGuard Home’s source).
5. Port configuration
All four LAN ports work as internal network ports by default. For a second WAN port, switch LAN 1 to WAN under Network → Ethernet Port, then choose Failover or Load Balance under Network → Multi-WAN.
Conclusion
On paper, the Flint 3 is a strong home router for those who want Wi-Fi 7 now and need multiple fast wired connections. The lower WireGuard figure compared to the Flint 2 only matters if your connection is faster than about 680 Mbps. This verdict rests on GL.iNet’s specifications and firmware, not on a hands-on test.
Next step
Chosen the Flint 3?
- GL.iNet travel router setup guide — step-by-step WireGuard, DNS-over-TLS and AdGuard Home configuration
Similar options
- GL.iNet Flint 2 review — previous generation, more WireGuard speed at a lower price
- GL.iNet Brume 3 review — if you don’t need Wi-Fi but want more VPN speed
- GL.iNet Flint 4 review — 10G ports and a higher VPN rating, at a higher price
Want to go further?
- Which network fits your profile? — how much router do you actually need?