![]() |
|
|
#2 (permalink) |
|
Posts: n/a
|
Thanks for the port! iw-scan looks like it will be handy. I often run with two boxes (linux or FreeBSD and W2K) and I've noticed that each one picks up different things better.
I don't have a Garmin GPS, some cheap Rand McNally thing....that doesn't seem to work with iw-scan. One question about wistat - how do you create that file? It looks like piping the output from iw-scan into a file will then let that file be read by wistat but then you can't see it on the screen at the same time. Can the output be sent to the screen and a file at the same time? I think maybe tee can do this....haven't figured it out yet though. |
|
|
|
#4 (permalink) |
|
Posts: n/a
|
I usually just do:
iw-scan > scanfile.wi & tail -f scanfile.wi Once I've got some more time to hack on iw-scan I'll see about making it go to both a file and stdout. I've also got to fix the Signal, Noise, and SNR data. No, there is no W2k version, you might as well use NetStumbler as its far better. wi-scan and iw-scan are both limited in that it ONLY reports the current associated AP which, is generally going to the be one with the strongest signal streangth. You a link to the lastest version is at: http://www.seattlewireless.net/index.cgi/WarDrivingSoftware |
|
|
|
#5 (permalink) |
|
Posts: n/a
|
Delayed response
Richard said:
"I usually just do: iw-scan > scanfile.wi & tail -f scanfile.wi" to use tee, do this: iw-scan > tee scanfile.wi tee takes the input and sends one copy to the named file and one to stdout. So, yes, you can further redirect this: iw-scan > tee scanfile.wi >> tee masterfile.wi This will put this scan in scanfile.wi, and *append* to masterfile.wi, and also to STDOUT (your screen). GNUbie |
|