Hide Forgot
Description of problem: NetworkManager takes much longer to get an address from DHCP than ifup does. On my wireless card, ifup varies between 2.9 and 7.1 seconds (over 10 tries). NetworkManager usually takes 16-17 seconds (3 tries). Version-Release number of selected component (if applicable): NetworkManager-0.3.3-1.cvs20050119.2.fc3 How reproducible: every time Steps to Reproduce: On my laptop with version 1.0.0 of the ipw2200 driver from ipw2200.sourceforge.net (ok, you can't do this part quite this way), try "time ifup eth1" and observe how long it takes (DHCP is complete before it finishes). Then bring eth1 down and try "service NetworkManager start" and look at how long the NetworkManager icon spins (which agreees with the messages in the syslog and the amount of time before I can resolve hostnames). Additional info: I'll attach a syslog excerpt that shows all the messages logged over this time interval.
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.