Doing the following on will cause some clients to have longer latency or skipped seq during ping
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
On a mt7615 we have ODBC enabled using phy1 as the 2.4 radio we have an AP setup on wlan1. We setup another interface on the same phy and do a site survey scan and after clients connected to the AP are slower to respond with ping. Latency increases and we see skipped seq.
iw phy1 interface add wlan99 type station
iwinfo wlan99 scan
iw wlan99 del
Any thoughts on why this happens?
We have a reason for setting up a second iface and we have done this successfully on a MT7620/7612 setup. Our setup is with a MT7621/7615
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on the described mt7615 setup using the iw and iwinfo commands for phy1, wlan1, and wlan99. Measure ping latency and skipped sequences before and during the site survey, then compare the behavior with the reported MT7620/7612 setup. Done means identifying and correcting the cause of client degradation during the scan, with the reproduction no longer showing increased latency or skipped sequences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100