# Flint 4 (GL-BE14000): forwarded LAN client gets ~2.4 Gbps where the router itself gets ~5 Gbps — but both together do 7.8 Gbps

**URL:** <https://forum.gl-inet.com/t/flint-4-gl-be14000-forwarded-lan-client-gets-2-4-gbps-where-the-router-itself-gets-5-gbps-but-both-together-do-7-8-gbps/71223>\
**Category:** Router\
**Created:** [September 11, 2026, 12:12pm UTC](https://forum.gl-inet.com/t/flint-4-gl-be14000-forwarded-lan-client-gets-2-4-gbps-where-the-router-itself-gets-5-gbps-but-both-together-do-7-8-gbps/71223 "2026-09-11T12:12:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaofl](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/45deac/32.png) [@joaofl](https://forum.gl-inet.com/u/joaofl)\
**Post date:** [September 11, 2026, 12:12pm UTC](https://forum.gl-inet.com/t/flint-4-gl-be14000-forwarded-lan-client-gets-2-4-gbps-where-the-router-itself-gets-5-gbps-but-both-together-do-7-8-gbps/71223/1 "2026-09-11T12:12:32Z")

</div>

Posting this because I can't find any published Flint 4 throughput data on the  
10G/SFP+ path — every review I found tested on 1–2.5 Gbps links and explicitly  
noted the 10G ports and SFP+ cage went untested. So this may be a gap worth  
filling, and I'd like to know whether others on multi-gig see the same shape.

**Short version:** a LAN client behind the router tops out around 2.2–2.9 Gbps to  
the internet, while the router itself pulls ~5 Gbps from the _same_ server on the  
_same_ port. But running both at once totals 7.84 Gbps — so neither the line nor  
the router's aggregate capacity is the limit. Hardware acceleration is on and  
binding flows, and the CPU is idle throughout.

## Setup

| | |
| --- | --- |
| Router | GL-BE14000 (Flint 4), firmware **4.9.1** |
| OS | OpenWrt 21.02-SNAPSHOT, kernel 5.4.281, mediatek/mt7988 |
| WAN | XGS-PON ONU stick in the SFP+ cage, **VLAN 131 tagged** , DHCP (10 Gbps plan) |
| LAN client | Fedora 44, Realtek RTL8127 10GbE (`r8169`), link 10000Mb/s full, MTU 1500 |
| Test target | `speedtest.init7.net` (Zurich, ~1 ms away), `iperf3 -P 8 -t 12 -R` |

Network Acceleration (HNAT) **enabled**. DPI **disabled**. No QoS/SQM. No VPN.

## Results

Alternating runs, same server, same port, back to back:

| Round | Router itself | LAN client (forwarded) |
| --- | --- | --- |
| 1 | 5.20 Gbps | 2.48 Gbps |
| 2 | 4.91 Gbps | 2.26 Gbps |
| 3 | 5.09 Gbps | 2.18 Gbps |

Reproducible ~2x gap. Then the interesting one — **both at once** , different  
server ports:

```auto
router : 4.53 Gbits/sec
client : 3.31 Gbits/sec
-----------------------
total : 7.84 Gbits/sec

```

Two things to note: the WAN clearly sustains at least **7.84 Gbps** , and the  
forwarded client ran **faster under contention** (3.31) than it ever does alone  
(~2.3). A simple forwarding bottleneck shouldn't behave that way.

Stream count helps a little but doesn't close the gap:

```auto
client solo, -P 8 : 2.24 Gbits/sec
client solo, -P 16 : 2.91 Gbits/sec
client solo, -P 32 : 2.67 Gbits/sec

```

## What I ruled out

- **Cabling** — `ethtool -S` error counters all zero on both hosts, hundreds of GB  
passed; both links negotiate 10000Mb/s full duplex.
- **Router CPU** — `top` during a forwarded transfer shows **97% idle**.
- **Hardware acceleration not engaging** — `/sys/kernel/debug/hnat/hnat_entry`  
shows the flows bound during the transfer (`PPE1 BIND cnt = 9`,  
`PPE2 BIND cnt = 8` for 8 iperf streams), NAT entries visible in both  
directions through the VLAN 131 WAN. `mtkhnat.global.enable='1'`.
- **DPI interference** — stopping `netifyd` changed nothing (1.98 → 2.06 Gbps).
- **Client NIC / MTU** — client was originally on MTU 9000, which forced `r8169`  
to disable TSO and TX checksum offload _and_ had oversized frames dropped by the  
router. Fixing it to 1500 raised the client's LAN transmit from 1.24 → 3.47  
Gbps, but did not change the forwarded-internet figure materially.
- **Test server** — the router pulls ~5 Gbps from the same server and port, and  
the simultaneous run shows 7.84 Gbps aggregate, so the server isn't the cap.

Solo forwarded runs do show meaningful retransmits (3,000–4,400 per 12–15 s run),  
which the router's own runs also show at higher throughput — so loss alone doesn't  
explain the ordering.

## Questions

1. Is ~2.2–2.9 Gbps expected for a **single** forwarded client on the Flint 4's  
10G path, or should it track the ~5 Gbps the router achieves itself?
2. Does anyone else running the SFP+ cage as a **tagged-VLAN WAN** (common for  
PON/ISP setups) see the same? I'd like to rule out the VLAN tag interacting  
badly with the offload path.
3. Is there a known reason the NPU would prioritise CPU-terminated traffic over  
hardware-forwarded traffic? A published Flint 4 review documented a related  
"cross-port forwarding vs CPU-termination asymmetry" on the same firmware,  
though in that case it only appeared under simultaneous load — mine happens  
with a single idle-router client.

Happy to run any additional tests or share raw iperf3/HNAT/`top` output. Reproducing  
this needs nothing exotic: two hosts, `iperf3` to a nearby public server, and  
comparing the router's own result against a LAN client's.

---

<div class="post-metadata">

**Author:** ![xize11](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/xize11/32/5340_2.png) [@xize11](https://forum.gl-inet.com/u/xize11)\
**Post date:** [September 11, 2026, 12:42pm UTC](https://forum.gl-inet.com/t/flint-4-gl-be14000-forwarded-lan-client-gets-2-4-gbps-where-the-router-itself-gets-5-gbps-but-both-together-do-7-8-gbps/71223/3 "2026-09-11T12:42:57Z")

</div>

hmm I do not have a direct awnser to this as I don't have 10gb from isp.

But there a few things you can still try to rule out if not done already:

- what is your utp cable rated at?, some cat6 maybe even cat7 have lower mhz rate than expected and maybe not fullfill the speed, or maybe has a rate which already decrease at distance.

- the length of the cable is also a important indicator, you want to test it via a short cable, not one like 10 20-50 meters or above that can increase also more chance of quality loss, just a simple 1m cable or lower than that.

also splitters or switches in between the cable you test should not be put in between.

---

<div class="post-metadata">

**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\
**Post date:** [September 11, 2026, 1:15pm UTC](https://forum.gl-inet.com/t/flint-4-gl-be14000-forwarded-lan-client-gets-2-4-gbps-where-the-router-itself-gets-5-gbps-but-both-together-do-7-8-gbps/71223/4 "2026-09-11T13:15:32Z")

</div>

Here is a community member who shared a test result of **8 Gbps+ on a PC with Flint 4** :

> [@Flint 4 BE-14000 Discussion Thread](https://forum.gl-inet.com/t/flint-4-be-14000-discussion-thread/70944/16):
>
> For anyone having doubts about Flint4 wifi capabilities, here's my testing runing on my Fold8, ideal conditions, 3 meters away, the flint is on a high location, no vpn, connected to MLO (5 and 6Ghz). Now running on the Flint directly (Maxed out Flints CPU capabilities since running here bypasses the HW acc and uses CPU) Running on my Desktop (10Gb NIC card)

Have you checked whether your PC itself has enough performance to sustain speeds above **10 Gbps**?

A long time ago, I encountered a case where a system could not even reach **1 Gbps** , and the cause turned out to be that the CPU was too old.

~~Also, if you are testing on Windows, it is worth checking the \*\*iPerf3 version/build\*\*. Some Windows builds have copy-related performance issues that prevent them from reaching high throughput:

[https://techcommunity.microsoft.com/blog/networkingblog/three-reasons-why-you-should-not-use-iperf3-on-windows/4117876](https://techcommunity.microsoft.com/blog/networkingblog/three-reasons-why-you-should-not-use-iperf3-on-windows/4117876)

 ~~

You may also want to try running an **iPerf3 server directly on the router** , or on another PC with a **10G-capable interface** , and test against that.

Edit: Just realized that the client is running Linux.
