View Single Post
Posts: 393 | Thanked: 67 times | Joined on Feb 2010
#42
lxp,

I sent the two files (kismet.log and dmesg.log) to you via private message (so I wouldn't be spamming this thread). The issue I am referring to is certainly reproducible (it happens nearly every time I am at the location which has 7 - 10 Cisco wireless access points and a handful of Wi-Fi clients.

Thank you

Originally Posted by lxp View Post
mail_e36,

Can you please run kismet_server separately and send me the output of it.
I would recommend running the following command:
Code:
kismet_server --no-line-wrap | tee kismet.log
This will start the Kismet server and create the file kismet.log while also letting you view the output of it on terminal.
In a second terminal start Kismet as usual, it should automatically connect to the running server instance.
It would also be good if you can send me your dmesg output. You can put it into a file with e.g.
Code:
dmesg > dmesg.log
Please also keep the other Kismet logfiles like Kismet-*.pcapdump, ... as they might be useful for further debugging, but I don't need them right now.



It is normal at least for now.