|
Really stuck with Kiswin32
Okay. I'm stuck. I've done a lot of reading and troubleshooting. Still stuck.
Here are *some* of the key things I've done:
I'm using w2k.
I've installed the kiswin32 package as indicated and extracted the .terminfo zip. I have the files currently at C:\Documents and Settings\Administrator\.terminfo - now, below that path I have a directory called "c" and then the three cgwin files from terminfo.zip reside in there.
I have tried it as C:\Documents and Settings\Administrator\.terminfo\.terminfo\c and also as C:\Documents and Settings\Administrator\.terminfo without the "c" directory.
What happens in all cases is that a dos window opens for a milisecond and closes, then a second one does the same after many seconds. I assume this is because something is wrong, and that is the result of no error handling per a snippet in one of the readme files indicating such a thing.
I have both tried the original kismet.conf file unchanged, and I have also tried it with the source defined. The readme seems rather clear that the file need not be changed, and it seems that the vb script will get the ip address to define the source. But after hours of trying everything, and getting kismet to run on the router itself, I had to try that. As was indicated in the readme I used a linux box (the wrt54g, actually) and vi to edit the file.
The computer does have a routable connection to the drone box - as I telnet in from a dos window from the same computer I'm trying to run kiswin on with no problems.
kismet _drone is running and indicates that it is listening. Currently I have it listening to 192.168.1.0/24, and have also had it listening to everything at 0.0.0.0/0.0.0.0 - I've also tried 192.168.0.0/24. (the router is at 192.168.1.1/24)
I have successfully connected a kismet_server running on the same wrt54g to verify that the drone is running and not the problem.
I always get the same result=NFG.
TIA for your direction on this...
-Mark
|