Reduce network startup and reconnect delays
@rslater-cs já está trabalhando nisso.
Desde 9/9/2026.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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.
- Linguagem predominante
- Lua
- Estrelas
- 1
- Forks
- 0
- Merge médio
- 5d 15h
- PRs com merge (30d)
- 3
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Sem guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de jangala-dev/devicecode-lua
-
wifi: 40 MHz HE/VHT htmodes unusable — validator only accepts HE40±/VHT40±, which OpenWrt 24.10 ignores (silent 20 MHz)Talvez já em andamento @rslater-cs assumiu há 1 dia. Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
jangala-dev/devicecode-lua#344 · 1 responsável ·
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 8/100
jangala-dev/devicecode-lua#339 ·
-
wired: comma-separated VLAN lists cause false missing-VLAN alertsTalvez livre de novo @rslater-cs assumiu há 43 dias e não há nenhum pull request aberto. Aberta
jangala-dev/devicecode-lua#333 · 2 responsáveis ·
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
jangala-dev/devicecode-lua#330 · 1 comentário ·
-
Track functional differences from devicecode v0.9.x and devicecode-lua v0.10.6 to v0.11.2Talvez livre de novo @rslater-cs assumiu há 49 dias e não há nenhum pull request aberto. Aberta
jangala-dev/devicecode-lua#329 · 2 responsáveis ·
Todas as issues de jangala-dev/devicecode-lua
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
lewis6991/gitsigns.nvim#1593 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
latex3/pdf_structure#28 · 4 comentários ·
-
Wrong step: Tirisfal Glades, step 6Talvez já em andamento Um pull request vinculado a esta issue está aberto ou já foi mesclado. Abertaguide
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
fitzforge/polestar#672 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
code health memtx mvcc
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia