feat: Enhance DHCP client timeout and retry logic #908
Conversation
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
ym
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The JetKVM DHCP client was taking 30+ seconds to acquire an IP address, causing delays to access the UI after boot.
1. Reduced DHCP timeout from 30s to 5s
DHCP servers respond in milliseconds; the 30s timeout was designed for physical interface initialization, not DHCP protocol operations. Added a separate timeout for the DHCP setup.
2. Added exponential backoff (1s → 2s → 4s → 8s)
After every 4 attempts per 5s, we sleep for an increasing amount of seconds, capped at 8s.
This makes the entire DHCP dance significantly faster.