MT7603E tweak dwell time
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
I am using MT7603E on stock Linux kernel v5.8.
I am using the driver in STATION mode using IWD.
If this is not the right place please redirect me as needed.
My problem is scan reliability.
Driver can detect very well some A.P.s (usually "quality ones") while it has difficulties finding others (especially HotSpots on low end cellphones).
It also has problems detecting multiple A.P.s on the same channel (testing is ongoing to ascertain this).
I noticed the whole scan seems to bevery fast (<4sec.) compared with usual scan times on other devices (tens of seconds on PC and over two minutes on some smartphone); I am wondering if this could be root cause of scan unreliability (i.e.: driver does not linger on the channel long enough to reliably catch beacons).
Can this really be a problem?
If so: how can I make DWELL time longer? Apparently driver does not support SCAN_DWELL or NL80211_ATTR_MEASUREMENT_DURATION and I failed (to date) to find where I can tweak the kernel source to this end.
Any comment would be welcome, especially so if you think I'm chasing ghosts.
Hardware is a Vocore2 module sporting a MT7628 SoC with a single antenna, if that matters.
Thanks in Advance
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
Start by reproducing scan reliability on the MT7603E/MT7628 hardware in STATION mode with IWD on stock Linux kernel 5.8, recording scan duration and detected access points. Inspect the driver's scan behavior and the reported absence of SCAN_DWELL and NL80211_ATTR_MEASUREMENT_DURATION. Done means establishing whether dwell time causes the missed networks and documenting a supported way to adjust it, if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100