Reduce network startup and reconnect delays
@rslater-cs ya está trabajando en esto.
Desde el 9/9/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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.
- Lenguaje dominante
- Lua
- Estrellas
- 1
- Forks
- 0
- Merge medio
- 5 d 15 h
- PR fusionados (30 d)
- 3
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de jangala-dev/devicecode-lua
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jangala-dev/devicecode-lua#344 ·
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
jangala-dev/devicecode-lua#339 ·
-
wired: comma-separated VLAN lists cause false missing-VLAN alertsQuizá libre de nuevo @rslater-cs la tomó hace 41 días y no hay ningún pull request abierto. Abierto
jangala-dev/devicecode-lua#333 · 2 asignados ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
jangala-dev/devicecode-lua#330 · 1 comentario ·
-
Track functional differences from devicecode v0.9.x and devicecode-lua v0.10.6 to v0.11.2Quizá libre de nuevo @rslater-cs la tomó hace 48 días y no hay ningún pull request abierto. Abierto
jangala-dev/devicecode-lua#329 · 2 asignados ·
Todos los issues de jangala-dev/devicecode-lua
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
luainkernel/lunatik#2018 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
LuaLS/lua-language-server#3481 ·
-
Kill Ishamuhale for Ishamuhale's FangPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertobug discord guide:04-the-barrens locale:enUS triage v0.2.6
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100