On Fri, 2010-01-29 at 10:36 -0500, Alexander Lam wrote:
On Thu, Jan 28, 2010 at 8:42 PM, Ng Oon-Ee <ngoonee@gmail.com> wrote:
Hi all, I'm using netcfg and recently have been noticing the following.
When I resume from suspend I call 'netcfg home' which tries to connect to my home's wifi network. ESSID and WEP key are correctly set. It exist with a 'could not obtain IP address error, this is the dmesg:-
Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: direct probe to AP 00:14:7c:be:39:ac (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:14:7c:be:39:ac (try 1) wlan0: authenticated wlan0: associate with AP 00:14:7c:be:39:ac (try 1) wlan0: RX AssocResp from 00:14:7c:be:39:ac (capab=0x471 status=0 aid=1) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present wlan0: deauthenticating from 00:14:7c:be:39:ac by local choice (reason=3)
The weird thing is that when I run 'iwconfig wlan0 essid MYESSID key MYKEY', then run 'netcfg home' again it works no problem. Suggestions for what I can check out are welcome. This happens both on stock kernel and my custom -ice kernel, am up-to-date (without testing for now, due to my openoffice variant not being done yet).
Perhaps you need to change DHCP_TIMEOUT in the network profile to be longer?
Thanks, I should have mentioned that this isn't a timeout issue, extending it to several minutes did not help, while once I run iwconfig prior to netcfg it connects in under 10 seconds.