AP scan utility

[Randale91]

Thanks a lot. Will you provide the sources also ?
Maybe we can share some knowledge about thread programming...
I like your tool and have some idea to add some enhanced features.

What do think about it ?

Best regards

[roadkiler]

Can anyone help me with this problem?

I have a wl500g with oleg's 1.9.2.7-7c and i receive always this message
"cannot connect to host".

I've tryed to access by telnet and all ok. My host isn't in the 192.168.xxx.xxx
is on 10.xxx.xxx.xxx.

i thinks thats no the problem, but... i don't know.

Regards

[Liszka]

Switch on logging and check the log file. If it doesn't help send the log file to me.

[digibrain]

Excelent !

Great job !

[schriss]

I tried it with my WL-500W and it says "can't connect", there is no log.

[Jack_Brody]

The same here, I got Wl-500gP (Oleg's FW 1.9.2.7-8 (2007-10-30)), and wl scan is of 1.0.1.0 version from 9 March 2006. I use WinXP.

I enter correct information:
host: 10.9.8.1
user name: admin
password: (my pwd, cannot tell you that, but it is not long and I am sure I am typing it correctly)

After a few seconds from clicking "Connect" I get: "Wrong username or password" and the password disappears from the box!!! If I use another IP, the password stays in.

Telnet with mentioned credentials works OK, I successfully log in.

Liszka, dont you know where the problem could be? The program doesn't generate any log even if I set it up to make one.

Maybe Delphi 2005 is the best choice, but probably not in this case...

[Liszka]

I must answer that the problem is not in Delphi itself but in the code . I know about it already some time but only few people sent their complaints. Now, already 3 people reported the problem and I decided to fix it. Give me several days please and you will get an improved version.

[Jack_Brody]

OK, looking forward to your next version. I'll test it immediately then.

[Liszka]

Please find the new version on the previous page. Let me know if it works better than before. Thanks.

[Jack_Brody]

Ok, so I have just tried new version (WL SCAN 1.1) from 2008 . I put in correct IP adress, username and password, after clicking on Connect I can see in the lower bar:

Connecting
Logging
Authenticating
GettingApMode

and then a window pops up with "ERROR: Could not get AP mode."

That's all for now.

Hmmm...I've also checked the "log to file" checkbox, but no log has been created. If you somehow get it to work, I will give you the log in the future. It would be probably much more of help for you.

I still have the same version of Oleg's FW as I wrote a few posts ago. And WinXP SP2.

[Jack_Brody]

The same happens no matter whether or not I check the "passive" checkbox.

[Liszka]

The log file is saved to "log.txt" after closing the tool. I can't test with 1.9.2.7-8 firmware now. The log usually looks like this if AP mode is off:

Asus login:
username
Password:

[username@Asus root]$
wl ap
ap is 0 (off)
[username@Asus root]$
wl scan -t passive
[username@Asus root]$
wl scanresults
SSID: "\x00\x00\x00\x00\x00\x00"
Mode: Managed RSSI: -57 dBm noise: -99 dBm Channel: 1
BSSID: 00:17:3F:07:C9:24 Capability: ESS WEP ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 11(b) 6 9 12 18 24 36 48 54 ]
WPA:
multicast cipher: TKIP
unicast ciphers(1): TKIP
AKM Suites(1): WPA-PSK
No WPA Capabilities advertised...etc.

Please send the log file to me or connect manually over Telnet and send the log of the session. Thanks

[Jack_Brody]

OK, after two connection tries the log contain following:

asus login: 
admin
Password: 

[admin@asus root]$ 
w
l ap
1
[admin@asus root]$ 
asus login: 
admin
Password: 

[admin@asus root]$ 
wl ap
1
[admin@asus root]$

When I connect manually via Telnet, I know how to obtain the list of neighbor wi-fi networks. I use these commands:

wl ap 0 (switch off the AP mode)
wl scan -t passive
wl scanresults
wl ap 1 (switching on the AP mode)

So I think if wlscan used the "wl ap 0" command first, it wouldn't have those problems. Just an idea.

[Liszka]

There is a new version on the previous page that should support the latest firmware (I hope). The difference is a more tolerant rule for reading AP mode (setting 'wl ap 0' had been included already earlier, the problem was caused by different format of the reply to 'wl ap' in different versions of firmware).

[Jack_Brody]

Yes!!!! Now it is working like a charm!! It connects in and then repeatedly scans the air and updates the table.

Perfect. Thank you Liszka, good work!