Hello everybody, Some days ago I`ve written a mail that the Kismet I`m running just fetches Beacon-Frames but no other data not even if I sit next to the PC of my friend who`s downloading whole ISOs (via WLAN).
I went to the IRC-Channel of the Kismet-Project and the author asked me to provide tcpdump-Logs. So I did switched the card into monitor mode (by hand via ifconfig) and started it up (also via ifconfig). THen I started tecpdump and on another screen kismet. And now the wonder happened: Now kismet can receive "data" (crypted) packets and not just beacon-Frames. But tcpdump is not logging anything even it`s running paralel. Setting the card by hand into monitor mode doesn`t affect kismets behavior because kismet is settign the card into promisc-Modus itself. So I4ve tested if it`s related to tcpdump and if I don`t start tcpdump before I do start kismet I don`t get other Frames except of the beacon-Frames (no data). But if I do run tcpdump on the other screen the tcpdump itself claims to receive no data (tcpdump -w LOG.raw -i ath0) and the logfile stays at 2KB (not growing). I`m using OpenBSD 4.0-Beta (installed ~ last weekend with the snapshot avaiable there) on a IBM Thinkpad R51 + a mini-PCI Atheros Card (from IBM). Are there any known issues with Atheros-Cards from IBM? I`ve no clue where the error could be. All I can say is that kismet works if I do start tcpdump first (but then tcpdump logs nothing). Any suggestions (because I don`t think that`s a normal behavior)? Kind regards, Sebastian
