Explore the guide library · Router configuration
Check documented feature conflicts before trusting counters or speed limits after changing packet-forwarding acceleration.
If router traffic counters or client limits behave unexpectedly after enabling acceleration, check the documentation before assuming the client is evading a rule. Some accelerated forwarding paths conflict with features that inspect or control traffic.
Read the exact compatibility note
GL.iNet’s current network-acceleration guide warns that client speed, traffic statistics and client speed limits do not work properly when that feature is enabled. Its SQM guide describes another incompatible combination. These are product-specific documented limits, not a universal rule for every router brand.
Decide which outcome matters
Write down whether the priority is maximum forwarding capacity, accurate household traffic accounting, a client limit or responsiveness under load. You may need a supported compromise or different hardware to achieve the required combination.
Compare settings methodically
- Record the original acceleration and traffic-control settings.
- Use one authorized test client and a repeatable transfer.
- Observe the relevant counter or limit.
- Apply only a documented compatible configuration.
- Repeat the same test and compare behavior.
Use an independent check
Where appropriate, compare the router’s observation with the endpoint’s own transfer information. Different measurement windows and protocol overhead can produce different totals, so avoid treating small differences as proof of malfunction.
If a provider charges by data usage, use its billing records as the authoritative basis for that charge. A home-router counter may have resets, missing paths or feature limitations.
Document the final choice
Keep a note of the feature combination and the reason for it. Retest after major firmware changes because supported behavior may evolve. Do not disable necessary security controls just to chase a higher throughput figure.
A useful configuration is one whose limitations are understood and whose important controls have been observed working. An impressive speed test cannot validate a traffic limit or a monitoring chart that the manufacturer explicitly marks as incompatible with the enabled acceleration mode.
Sources and editorial notes
Sources checked 8 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.
- GL.iNet: network acceleration feature conflicts
- GL.iNet: Smart Queue Management and hardware limitations