The same happens no matter whether or not I check the "passive" checkbox.
Printable View
The same happens no matter whether or not I check the "passive" checkbox.
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 :)
OK, after two connection tries the log contain following:
Code: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.
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).
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!
Well, one thing: when scanning the AIR LED is blinking. When I click on "Disconnect", the LED stays unlit (!). After restart of the whole router the AIR lights up again.
I cannot confirm if this is a problem (if that means the radio is switched off) as I don't have any wi-fi client device to try at the time.
Please check again the log file, whether 'wl ap 1' command is sent before disconnecting. It should if the router had been in AP mode before the scanning started (indicated as the result of 'wl ap' in the beginning of the log).
Yes, the last command issued is "wl ap 1". Anyway, AIR always turns off.
Hi all,
It work fine now for the newest firmware.
Hi All!
Unfortunately, I couldn't connect to my router with WL SCAN utility. The error message is: "Could not connect to the specified host", but I write valid data to host/user/pass-fields. How can I solve the problem?
Config: Asus WL-500G/Oleg-1.9.2.7-9
Thanks for help..
zitev
I have the same problem in version WLScan 1.1 (2008) - "ERROR: Could not connect to the specified host". No log was created after exiting application :(
Try enable telnet access on router system setup/services menu.
(ohh i don't know where can you find that option on tomato firmware...)
hi i have some problem, everything looks good but nothing happened. no results.
i have oleg WL500gpv2-1.9.2.7-10
log.txt
Router login:
admin
Password:
[admin@Router root]$
wl ap
0
[admin@Router root]$
wl scan -t passive
[admin@Router root]$
wl scanresults
wl: Not Ready
[admin@Router root]$