openwrt / openwrt/mt76

MT7986 - temporarily ping spikes and terrible WiFi performance - 5GHz, 160 MHz

Open
#877 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
888
Forks
436
PR merge metrics
No merged PRs in 30d

Description

Subject of the issue

Massive ping spikes and a bad WiFi performance (<50Mbit) are randomly occurring with the MT7986 chipset on both bands

Your environment
  • MT6000 & TUF-AX6000
  • Latest snapshot (r26128) & 23.05.3
  • Public WiFi
  • WED disabled, no software or hardware offloading, 5GHz, 160MHZ, client isolation on
Expected behavior

Stable and fast WiFi performance during the "good times":

image

image

Actual behavior

image

image

I'm having random horrible ping and WiFi performance problems with the MT7986 driver. This happens on the MT6000 and also the Asus TUF-AX6000 with all 5GHz and also sometimes 2.4 GHz clients, which are connected at the same time. The problems always occur every 10-30min lasting for around 5-10min until everything returns to normal. No errors in the logs. Via LAN cable the connection is always fast and stable.

This problem happened so far with every OpenWRT version which i tried. It does not happen with the stock firmware of both devices.

I have the feeling that its caused by specific WiFi clients, but it also seems to happen when AP-STA-POLL-OK is being sent.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MT7986 driver and reproduce the reported 5GHz 160 MHz behavior on the MT6000 or TUF-AX6000 using the listed OpenWrt versions and client-isolation settings. Compare the affected WiFi behavior with the stable LAN connection and observe whether the 10–30 minute degradation coincides with AP-STA-POLL-OK; done means identifying and correcting the cause of the recurring spikes and throughput loss.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.