Joachim Ott wrote: > 2009/3/5 Daniel Benoy <dan...@benoy.name>: >> Also, I rebooted the thing and it got an IP just fine. (!?) Also I see >> that it got alerted through the wpa_cli action stuff at boot time just like >> I was expecting it to do earlier... >> >> I'm working on the theory that the timeout in wpa_supplicant is too short.. >> it would explain the flakyness. Unfortunately the timeout value is hard >> coded, so I'll have to mess around to test that. >> >> also 'iwconfig eth0 power off' seems to make the issues go away. All this >> intermittant behavior is reinforcing my theory that the timeout is too short >> and various factors make the time it takes shorter or longer causing >> intermittant behavior. >> >> Shame on wpa_supplicant for not making the timeout configurable. > > If this is really an open AP, you don't need to hassle with > wpa_supplicant, just do: > > iwconfig eth0 essid kitsune > > Then use dhclient to get an IP.
Sometimes it's useful to force the removal of any previous key: iwconfig eth0 essid kitsune key off _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
