Bump WiFi client connect timeout from 30s to 60s - #71
Open
eliasbakken wants to merge 1 commit into
Open
Conversation
Observed a real timeout on a 5GHz network in practice: the boot-time connection attempt hit the full 30s window and fell back to hotspot, even though the network was reachable and reconnecting manually succeeded moments later. 5GHz scanning (particularly across DFS channels, which require slower passive scanning) can plausibly eat into a cold boot-time connect more than 30s comfortably allows. The cost is asymmetric: a longer timeout just means a slightly longer boot delay in the rare case the SSID truly isn't reachable, but a too -short timeout means falling back to hotspot even when the network would have connected given a few more seconds - which then needs manual intervention to fix, defeating the point of #65's design (hotspot is meant to be a last-resort backup, not something to hit routinely). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Observed a real timeout on a 5GHz network in practice: the boot-time connection attempt hit the full 30s window and fell back to hotspot, even though the network was reachable (reconnecting manually right after succeeded within a few seconds).
5GHz scanning - particularly across DFS channels, which require slower passive scanning - can plausibly eat into a cold boot-time connect more than 30s comfortably allows.
Why 60s
The cost is asymmetric: a longer timeout just means a slightly longer boot delay in the rare case the SSID truly isn't reachable at all, but a too-short timeout means falling back to hotspot even when the network would have connected given a few more seconds - which then needs manual intervention to fix. Per #65, the hotspot is meant to be a last-resort backup, not something to hit routinely.
🤖 Generated with Claude Code