Follow-ups left open by the station identity seam (#460)

Aperta
#461 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, linux

Direzione di ricerca

Start with the named entry points IRadio::SetStationIdentity, Mt7612uRadio::StartRxLoop, src/sta, and the scripts tests/mt7612u_sta_uplink.sh and tests/mt7612u_sta_identity.sh; the issue also points to gate_txs from #452. First identify one bounded follow-up, then review the existing measurements and harness requirements. Done criteria depend on the chosen item; for station behavior, the issue specifies both addressed-station receive/acknowledgment and the station's own unicast acknowledgment.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Follow-ups left open by #460 (IRadio::SetStationIdentity, the MT7612U station arm, merged as 77b907a). None blocks the seam; each is a measurement or a port that the PR named and did not do.

Library

  • The Realtek station arm. SetStationIdentity returns the not-ported false on Jaguar1/2/3, Kestrel and the RTL8733B. On Realtek the MACID / BSSID registers and the ACK responder relate differently from the MT7612U's port identity, so the seam needs its own measured arm per family, with the same two halves of the bar (station_mode_ok): unicast addressed to the station received and acknowledged, and the station's own unicast acknowledged.
  • A role-selected managed receive filter on the MT7612U. Mt7612uRadio::StartRxLoop installs the monitor filter unconditionally, so a station driven through IRadio runs promiscuous and never runs the managed filter 0x00015f97 the cells measured. "Moving the port identity makes a station deaf" is a managed-filter property; under the monitor filter it keeps receiving and stops acknowledging.
  • The src/sta caller. Nothing in-tree calls SetStationIdentity yet. The station harness that associates through IRadio over the src/sta core (frames, supplicant, CCMP, DupDetector) is what exercises the arm-then-measure path the cells did not run, and is where the tx.retry_limit == 0 warning gets bench-checked.

Measurements

  • The BSSID receive table on a second rig. The second unit (CF-922AC, 40:a5:ef:5f:65:51) reproduced staid, autoack, uplink and staack arm C, but the sta table stalled twice on an rtw88 AP (RTL8812BU on a SuperSpeed root port, failed to get tx report from firmware; injector at 100/s and 8/s of 300). The harness refused both, correctly. A non-rtw88 AP (vendor rtl88x2bu built for the rig kernel, or a non-Realtek AP) is needed to reproduce the table off the author's rig.
  • The 6 fps txs gate loses one status entry per arm on the second unit. Every ~6 fps arm reads 199/200 (or 59/60) while the high-fps arms settle 200/200; the author's unit settles all of them. tests/mt7612u_sta_uplink.sh refuses any deficit on a claiming arm, so on that unit the uplink half of station_mode_ok's bar is INCONCLUSIVE 3 runs out of 4 with arm A at 199/200 acknowledged, 0.0 mean retries, against 0/158 at 16.0. Either find the lost entry in the status-FIFO drain (gate_txs, from #452) or give the claiming arm a bounded tolerance.
  • Uplink mean retries differ between units: 0.0 on the author's, 1.9 on the second (cc48be4 run, 60/60). Stated in the doc, unexplained.
  • The unexplained first-arm excess. Arm A of the BSSID table sits 4–7% above B–F in every run; with one run per arm it cannot be separated from drift, and a real few-percent BSSID-register effect would hide inside it.
  • Unassociated cells only. Power save, TIM parsing, cross-BSS duplicate detection and hardware key lookup are untested on the MT7612U.

Harness

  • tests/mt7612u_sta_identity.sh's rig requirement ("both adapters at high speed, no full-speed hub") is necessary, not sufficient: the rtw88 stall also happened on a SuperSpeed root port.
Lingua principale
C
Stelle
56
Fork
29
Merge medio
3h 43m
PR unite (30g)
75

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenIPC/devourer

Tutte le issue di OpenIPC/devourer

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.