yenjung at gmail.com
Wed Mar 2 22:02:27 EST 2005
On Thu, 3 Mar 2005 10:41:14 +0800, YenJung Chang <yenjung at gmail.com> wrote:
> Hi, List and Jouni,
> I tested wpa_supplicant with ap_scan=1 and ap_scan=2, and it seems
> there is some problem on ap_scan=2.
> The testing steps on ap_scan=1 and ap_scan=2 are same:
> 1. $ wpa_supplicant.conf -i ath0 -c/etc/wpa_supplicant.conf -d > supp1.log
> 2. $ wpa_cli status (make sure the connection is created)
> 3. $ wpa_cli reassociate ( force wpa_supplicant to reassociate)
> 4. $ wpa_cli status (check is it connected?)
> The connection with ap_scan=1 is re-created successfully, but failed
> with ap_scan=2.
> Following is my wpa_supplicant.conf
> and attached supp1.log is the log when tested ap_scan=1 and supp2.log
> is ap_scan=2.
> Is it meaning there is some problem on ap_scan=2?
> There is another stranger behavior on ap_scan=2. The connection to AP
> is hard to create
> if the wpa_supplicant commad is "wpa_supplicant -i ath0 -c
> /etc/wpa_supplicant.conf -d",
> but the connection is created successfuly if the command is
> "wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf -d > /tmp/supp2.log".
> The only difference is that the output log is redirected to a file.
> I have no idea what cause that. And I can not post the failed log, bcz
> it would not fail when I redirect the log to a file. :S.
One thing missed. The used driver is Madwifi.
More information about the HostAP