Bug 148751
Summary: | NetworkManager takes too long to get address via DHCP | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Baron <dbaron> | ||||
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-05-16 20:13:55 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Baron
2005-02-15 08:15:46 UTC
Created attachment 111077 [details]
excerpt from /var/log/messages showing 16 seconds to get DHCP address for eth1
So the whole connect process takes about 25 seconds? This is somewhat fixed in later builds of NetworkManager (latencies have been reduced) and is more fixed in CVS HEAD. Some of the issues are the cards themselves and the difficulty of figuring out if you really are connected to the access point or not. The actual DHCP transaction took only 2 seconds (it starts with the dhcp_interface_init line at :54). From :38 -> :54, the card is being set with the correct wireless settings. Some cards, like Prism54, reboot themselves after setting the ESSID and you have to wait. You also have to wait for a valid connection to the access point. |