Follow-ups left open by the station client (#464)

Ouverte
#465 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
c, linux
Domaine
backend, testing

Piste de recherche

Start with the station client over IRadio in src/sta and the headless cells in tests/mt7612u_sta_onair.sh; the issue lists race handling, Realtek DUT support, a reconnect cell, throughput testing, and a soak as separate follow-ups. First read the merged #464 work and its review context to identify which item to take on. Done means implementing one scoped follow-up and adding or updating headless coverage; the issue does not specify acceptance criteria for all of them.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement

Left open by #464 (merged as 927cfc7): the station client over IRadio + src/sta, its headless cells and tests/mt7612u_sta_onair.sh.

From the review

  • Back-to-back hostapd restarts race the AP interface. cell_end returns as soon as the hostapd process exits and ap_up launches the next one at once. One restart in four on the review rig started 30 ms after the previous AP-DISABLED and died with Could not read interface wlp13s0u2 flags: No such device / nl80211 driver initialization failed (scored INCONCLUSIVE, correctly). Wait for the netdev to be present and type managed before launching, or retry once on that failure. Fits the sibling-harness cleanup PR the author mentioned (INT trap not exiting in mt7612u_ap_onair.sh, hostapd left running when mt7612u_sta_identity.sh is interrupted during AP start, hand-back while the process is alive, unbounded waits).

From the PR description

  • Realtek DUTs in the on-air cell. The client arms an 8822C / 8822B through the #463 arm, but sta_dut_take is MT7612U-only; a generic DUT take / hand-back is needed before the cell can cover them.
  • A reconnect cell (AP stopped and restarted): the re-join policy is pinned headlessly only.
  • Software-CCMP throughput under load, and a long soak with the default retry settings.

Unscored observations

The noarm and retry0 INFO lines (link outcome, not scored) read 0 % loss on most runs, 33 % and 16.7 % once each. Six pings at near field is a sample; if these cells ever score the link, they need a real measurement window first.

Langage dominant
C
Étoiles
56
Forks
29
Merge moyen
3 h 43 min
PR mergées (30 j)
75

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de OpenIPC/devourer

Toutes les issues de OpenIPC/devourer

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.