Follow-ups left open by #452 and #454 (radiotap ACK request / MT7612U retries, station core)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 15/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- c
- 領域
- networking
研究方向
This issue tracks several independent follow-ups rather than one bounded change. Start with the relevant entry points named in the issue, such as RtlJaguarDevice.cpp, src/mt7612u/tools/bringup.cpp, and docs/mt7612u-tx-retry.md, and confirm with the maintainers which item is still wanted before starting. Done depends on the selected follow-up; the issue spans driver behavior, station-core integration, protocol security, and missing test coverage.
由索引模型根據 Issue 內容生成。
描述
Follow-ups the two PRs named or left open, so they are tracked somewhere other than the merged descriptions.
From #452 (radiotap ACK request + MT7612U retry limit, 8a47362)
- Port the radiotap TX_FLAGS NOACK / ACK-request choice to the Realtek TX descriptors: Jaguar1 first (BMC is unconditional there,
RtlJaguarDevice.cpp), then Jaguar2/3, Kestrel and the RTL8733B, sobuild_stream_radiotap(mode, false)means the same thing on every backend. Today only the MT7612U reads the bit. -
examples/chanmigbecomes the first in-treeno_ack=falseconsumer as soon as it sends any frame unicast to the peer's responder address (everything it builds today is a broadcast probe request, so NOACK is correct there). - The ~20 ms per-frame cost of one-way unicast injection on the MT7612U is not the retry ladder (0 retries measured off
MT_TX_STAT_FIFO) and is still unexplained; candidates not yet separated: per-WCID serialization with the 0xff no-station index, TXOP/EDCA admission for a unicast RA, lazy USB completion.docs/mt7612u-tx-retry.md"The open question". - The one-step TX-status lag in
mt7612uprobe txs(status visible only after the next submit vs an EXT/FIFO pairing off by one) is characterised but not explained. - Nit:
txs_parse_longinsrc/mt7612u/tools/bringup.cppcarries a stale duplicate comment block above it (the first one describestxs_retry_limit_env). - The NOACK-vs-ACK delivery table (0/5386 lost with ACKs requested) came from an associated-client harness + AP-side ledger that are not in the tree; make it reproducible once a station consumer lands.
From #454 (device-free station core, 956e723)
- A consumer: nothing in the tree drives
StationSmagainst a radio yet.DupDetectorandmsdu_to_eth/eth_to_msduhave no in-tree caller either, and the data-plane caller must run one duplicate cache per transmitter itself. - AP-side multi-station table (per-station PTK, TX PN, replay state), deliberately left out.
-
CcmpReplaywindow is 64 PNs (HT/VHT BlockAck); must be widened before any HE/EHT peer negotiating 256/1024. - The IEEE 802.11-2016 Annex J.4 CCMP vector is still not in the tree (copy from the standard or hostapd's wlantest vectors, never from memory); the kernel captures are an interop reference, not the spec.
- No captured hostapd group rekey; that path is pinned only by the same-author fixture.
- PMF / 802.11w: an MFP-required BSS is not selected and deauth/disassoc are accepted unauthenticated.
- A forged message 1 replaces the single in-flight candidate PTK (same exposure as wpa_supplicant's TPTK); during a PTK rekey on an established link it can cost the link.
- 主要語言
- C
- 星號
- 56
- 分支
- 29
- 平均合併
- 3 小時 43 分鐘
- 30 天內合併 PR
- 75
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
OpenIPC/devourer 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)可能已有人在做 @josephnef 今天認領。 未關閉enhancement
難度 4/5 3-5 天 新手友好度 42/100
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 12/100
OpenIPC/devourer#579 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 5/5 一週以上 新手友好度 12/100
維護者通常 1 天內回覆
-
enhancement
難度 5/5 一週以上 新手友好度 8/100
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
Needs-Triage
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 2 天內回覆
-
issue: bug report
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 2 天內回覆
-
cross-platform fix-now
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
feature:index kind:crash status:confirmed triaged
難度 2/5 1-3 小時 新手友好度 77/100
維護者通常 1 天內回覆