Reduce network startup and reconnect delays
@rslater-cs y travaille déjà.
Depuis le 9/9/2026.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
Network interfaces take too long to become usable and show online after boot or modem reconnection. Remove avoidable delays between modem readiness, interface publication, network activation and UI status updates.
Evidence
Observed on BigBox SS with firmware bigbox-ss-v0.11.2-2026-09-09T103923-v22.03.7, including the HAL late-reply fix from #331:
- GSM discovers and publishes the modem's network interface during its metrics poll. That loop waits before its first iteration; BigBox SS configures a 60-second interval. See interface discovery, initial polling delay, and target configuration.
- During SSH observation on 9 September 2026, primary was detected at 14:47:39 UTC, but its
wwan0binding was not published until 14:48:41 UTC. ModemManager had already reported the modem connected at 14:47:46 UTC. - Separate modem arrivals trigger successive structural network applies. In the initial logs, secondary arrived at 14:38:22 UTC, primary superseded its apply at 14:38:24 UTC, and the replacement took 27.1 seconds.
- Structural applies reload networking and restart dnsmasq, firewall and mwan3. Logs show existing WAN and cellular connections temporarily disconnecting during these applies.
- Publishing GSM connection state also performs synchronous diagnostic reads, which can delay state delivery when modem requests are slow. Their contribution to the observed delay needs measurement.
The 60-second dependency predates #331. Keep that deadlock fix. Manual SIM swaps may explain the observed modem disappearances; this issue focuses on startup and recovery latency, not diagnosing those disappearances.
Requested improvements
- Discover and publish the network interface promptly during modem initialization and reconnection, independently of periodic metrics.
- Publish essential connection state without waiting for firmware, band, operator or signal enrichment; update diagnostics separately.
- Coalesce closely spaced interface changes and avoid unnecessary service restarts or repeated activation work.
- Measure elapsed time from modem detection through APN connection, interface publication, network activation and UI readiness using monotonic timestamps. The initial boot logs include a wall-clock correction, so wall-clock timestamps alone are insufficient across that transition.
Acceptance and validation
- Healthy interfaces become available without waiting for a metrics interval or optional diagnostic reads.
- Test cold boot, devicecode restart, SIM reconnection, and both modems arriving close together.
- Slow diagnostics on one modem do not delay readiness reporting for the other.
- Verify actual network readiness alongside UI status, and record before/after timings.
- Add focused GSM/network regressions and run the Lua suite. Preserve existing public interfaces and the #331 deadlock fix.
- Check the shared behavior for
bigbox-ss,bigbox-v1-cm, andbigbox-v1-cm-2; identify which targets receive hardware validation.
Related: #330 tracks the separate case where mwan3 is already online but the UI remains offline. Coordinate the fixes while distinguishing actual connection latency from stale UI status.
- Langage dominant
- Lua
- Étoiles
- 1
- Forks
- 0
- Merge moyen
- 5 j 15 h
- PR mergées (30 j)
- 3
Préparer son environnement
Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Aucun guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de jangala-dev/devicecode-lua
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
jangala-dev/devicecode-lua#344 ·
-
enhancement
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 8/100
jangala-dev/devicecode-lua#339 ·
-
wired: comma-separated VLAN lists cause false missing-VLAN alertsPeut-être à nouveau libre @rslater-cs l’a pris il y a 42 jours, et aucune pull request n’est ouverte. Ouverte
jangala-dev/devicecode-lua#333 · 2 personnes assignées ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
jangala-dev/devicecode-lua#330 · 1 commentaire ·
-
Track functional differences from devicecode v0.9.x and devicecode-lua v0.10.6 to v0.11.2Peut-être à nouveau libre @rslater-cs l’a pris il y a 48 jours, et aucune pull request n’est ouverte. Ouverte
jangala-dev/devicecode-lua#329 · 2 personnes assignées ·
Toutes les issues de jangala-dev/devicecode-lua
Issues similaires
-
guide
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
fitzforge/polestar#672 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Witch 2Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 91/100
LuaLS/lua-language-server#3482 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 2 jours
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
luainkernel/lunatik#2018 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 78/100