#13385 closed bug (fixed)
First DHCP lookup times out when to connecting to WIFI
Reported by: | tqh | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Servers/net_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
When connecting to wifi, first DHCP lookup fails. As its timeout is four seconds, it takes a long time to connect.
Not sure why it fails, probably fails to send first packets. I made a patch to DHCP which timeouts after a few mS and it connects four seconds faster.
Attachments (2)
Change History (15)
by , 8 years ago
Attachment: | dhcp_test.patch added |
---|
comment:1 by , 8 years ago
patch: | 0 → 1 |
---|
comment:3 by , 8 years ago
Component: | - General → Servers/net_server |
---|---|
Owner: | changed from | to
comment:4 by , 8 years ago
Would be nice to find the cause of the first failure, but there is little that speaks against using a more aggressive retry interval here. It's used to reduce the load of the server when many clients going through a DHCP negotiation at once -- since current hardware is much more capable, and since this happens quite rarely anyway, I'm all for a shorter cycle.
comment:5 by , 8 years ago
Yes, not sure how to track the failure down easily though. If anyone can check if it also fails on first try on cable (I don't have hardware) we'd have some more clues.
comment:6 by , 8 years ago
Proposing these changes to dhcp-client, I changed the max comparison to a min one as it just seemed wrong to me.
comment:7 by , 8 years ago
We are getting 'Operation timed out' but bytes received are not < 0 here: http://cgit.haiku-os.org/haiku/tree/src/servers/net/DHCPClient.cpp#n683
So no if case is taken.
comment:10 by , 8 years ago
patch: | 1 → 0 |
---|
comment:11 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:12 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Remaining issues tracked in #14307.
comment:13 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Very short initial timeout