Fix High Gaming Ping on OpenWrt Routers: Start Simple, Then Optimize

You installed OpenWrt, but games still lag. Downloads are fast, yet your character snaps backward. Someone starts uploading photos, and your ping suddenly spikes. This does not necessarily mean your router is configured incorrectly or needs replacing.

Separate two questions: is traffic queuing inside your home connection, and is the route beyond your router stable? Local adjustments can help with the first. The second requires checking the connection to the game server.

Start with the easiest checks below. If one solves the problem, stop there. You do not need to install every available feature.

Step 1: Use Ethernet to Rule Out Wireless Problems

If you normally play over Wi-Fi, temporarily connect your gaming device to the router with an Ethernet cable. Keep the same game server and test the situation where lag usually occurs.

• Ethernet is noticeably steadier: focus on wireless coverage, interference, and access point placement.
• Both connections are unstable: continue with background traffic and external connection checks.
• The picture stutters without a corresponding rise in network latency: check device performance first. Router settings will not fix low FPS.

If Ethernet is unavailable, test closer to the router. Full signal bars do not guarantee an interference-free connection.

To check the connection between a Windows computer and the router, open Command Prompt and run:

ipconfig

Find the Default Gateway under the adapter you are using, then test that address. For example:

ping -t 192.168.1.1

Replace the example with your gateway address. Press Ctrl+C to stop.

This tests the router’s response, not the game server’s latency. One timeout does not prove that a cable or router is faulty. What matters more is whether repeated irregular replies coincide with interruptions in the game.

Step 2: Pause Transfers and See Whether Ping Recovers

Pause cloud syncing, photo backups, game downloads, and video uploads. Check other devices in the household too.

If the game becomes stable afterward, the issue may not be a lack of speed. Game packets may be waiting behind other traffic.

Think of your connection as a road. Bandwidth describes how much traffic it can carry; latency reflects how long a packet takes to arrive. Even a wide road can develop a queue.

Try a simple comparison:

1. Observe game latency and responsiveness without large transfers.
2. Start an upload, watch for changes, then pause it.
3. Test a download separately and compare the result.

Testing upload and download separately helps identify which direction needs attention. Do not run this experiment during a ranked match.

If pausing a backup is enough to restore normal gameplay, schedule it for another time or limit its speed in the application. Continue to SQM only if gaming and other transfers need to run together.

Step 3: Use SQM to Reduce Queuing Under Load

Smart Queue Management, or SQM, mainly addresses connections that work well when idle but develop high latency during uploads or downloads.

It does not create more bandwidth. Instead, it holds traffic below the connection’s available capacity so that queuing can happen where the router can manage it. Peak download speed may drop slightly; the goal is better responsiveness while the connection is busy.

Start With These Settings

Back up your router configuration first. Install sqm-scripts and luci-app-sqm from the package repository appropriate for your firmware. The settings are usually available under Network → SQM QoS in LuCI.

Then work through these steps:

1. Select the interface carrying internet traffic. Check your WAN configuration rather than copying someone else’s interface name. Connections such as PPPoE may use different names.
2. Measure actual download and upload speeds. Use Ethernet and pause transfers on other devices. Do not rely only on your plan’s advertised speed.
3. Set shaping rates below the measured capacity. Around 90% can serve as a starting point. Adjust afterward based on latency under load.
4. Check the units. If the fields use kbit/s, multiply your measured Mbps figure by 900 to calculate a 90% starting rate.

For example, measured speeds of 100 Mbps download and 20 Mbps upload give:

Download: 90000 kbit/s
Upload:   18000 kbit/s

These are conversion examples, not recommended values for every connection.

Choose the queue discipline, script, and link-layer settings according to your OpenWrt version and connection type. Do not enable unfamiliar advanced options merely because they sound useful.

Repeat the Earlier Transfer Test

Run an upload or download again and observe whether game latency is steadier.

If the improvement is clear, you do not need to keep adding settings. If spikes return during peak hours, the connection’s available capacity may have fallen below your shaping rate. Recheck it under those conditions.

For the SQM test, review flow offloading settings and temporarily disable both software and hardware flow offloading to remove them as variables. Some traffic may otherwise avoid the expected queue-processing path. Throughput can decrease with offloading disabled, so monitor router load as well.

Step 4: Make Sure the Router Can Keep Up

SQM requires CPU processing. More features do not always mean better performance, especially on an older router handling a fast connection.

If enabling SQM causes a large speed reduction or worse responsiveness, check processor load in LuCI. A modest overall average does not necessarily rule out a busy individual core.

Lower the shaping rate and temporarily stop unnecessary extra services, then compare again. If stability returns at a lower rate, investigate the router’s processing capacity rather than adding more features.

Do not replace the router at the first sign of reduced speed. First distinguish the expected shaping margin from a device that cannot handle your target rate.

Why Can Ping Stay High When the Local Network Is Fine?

SQM manages queuing and bandwidth at your home connection. It does not directly choose the nodes used inside your provider’s network or move a distant game server closer.

Beyond your router, packets still travel through external networks. Even without local congestion, a particular game route may be indirect or congested. Working websites and videos do not prove that the game connection is healthy because their destinations and traffic requirements differ.

This is where the GearUP OpenWrt plugin can become a further optimization option.

OpenWrt router installation guide

The two tools address different parts of the connection:

• SQM aims to reduce waiting caused by competing household traffic.
• The GearUP plugin attempts to provide a more suitable connection path for supported games.

However, a healthy LAN does not prove that every remaining delay is routing-related. Check game maintenance, server status, and your selected game region too.

How Does the GearUP Plugin Help in Practice?

Its biggest advantage is its worldwide network of proprietary nodes. When your data travels through your ISP’s default nodes, indirect routes are often unavoidable. ISPs do not tailor a dedicated route for every player and game server.

Through dedicated services and game-specific optimization, the GearUP plugin dynamically assigns nodes in real time to improve stability and reduce latency. This offers particular advantages for complex connections across regions. You may see:

• Lower packet loss
• More stable ping
• Fewer connection failures

At the same time, its extremely simplified usage allows you to complete the installation with just a single command line and use it long-term without needing to adjust settings every time.

Do Not Judge Success by the Lowest Ping Alone

Return to the situation that originally caused trouble.

If household uploads no longer trigger sudden lag, traffic management may be helping. If fluctuations decrease on the same game server, route optimization may be useful. If only visual stuttering remains unchanged, return to device-performance troubleshooting.

The useful result is that the original problem happens less often. Keep changes that help and undo those that do not. That is more effective than filling the router with features.