On Mon, 16 May 2005, Andrew McMillan wrote:
- iwlist wlan0 scan sometimes misses the net I am looking for.
There is unfortunately nothing I can do about that unless you can provide me with some guidelines about how it can be reliable. For example, in my own case, iwlist ... scan always fails unless I "ifconfig ... down; sleep 4; ifconfig ... up" first. Bizarre, but it works :-)
I think it might have something to do with how long it scans on each channel, but I am not really sure about that. We have a very rich WLAN environment here, with at least 4 different networks on air all the time, so perhaps that influences the scan somehow. The man page for iwlist says something about the driver configuration influencing the scan, so I guess it might depend on the threshold values in iwconfig nad perhaps some other things, but I would have to examine that in detail to get any meaningful results.
The point is though that I can only make these sorts of empirical observations about hardware I have access to. If you can work out any further details regarding this, can you please create a new bug report with what you've discovered.
ok, this may take a while.
- IDs including a space like "wireless Extreme" can only be passed to testap using a wildcard pattern, but then the scan problem kicks in, and it looks as if then the wildcard pattern is used as ESSID. I was able to change the network id as a workaround.
There is supposed to be code in testap to handle this, and I can't see where it's going wrong. If you are able to duplicate the problem for me can you file a new bug, and provide the output of "whereami --scriptdebug", to assist me in solving it. Send that to me privately if you are worried about exposing it to the world!
well, the first problem is that I can't simply put the ESSID in
detect.conf, since all behind the space is then recognized as a target
token. If I put quotes around the id, the egrep statement gets syntax
errors. If I put in a wildcard, the scan fails and the ESSID does not get set. So maybe changing the detect.conf syntax to include quotes
around the ESSID would be the easiest way, especially since it is a
bit difficult to get information about what might be a valid ESSID
string. I did a quick web survey and did not find anything, so I guess
all sorts of non-alphanumeric characters could be allowed.
But I'll do a test run with a space-included ESSID later and send you the
results.
-- peter koellner <[EMAIL PROTECTED]>
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
