Kismet Wireless

Kismet Forums

 

Posted by:racelife
Subject:finally got kismet up but nothing on u.i. (backtrack2f)
Date:19:33:59 15/11/2007

card monitoring nothing in u.i. just upgraded to latest kismet and edited source in two diferent places but output said "none specified" tried kismet-ng command now u.i. comes up but nothing happens.... ive searched and searched and cant find anything im kind of new to linux but pretty intelligent and can figure most things out
setup:
old gatewa laptop
backtrack2f hard drive install
atheros card d-link dwl-650

output:

Launching kismet_server: /usr/local/bin/kismet_server

Suid priv-dropping disabled. This may not be secure.

No specific sources given to be enabled, all will be enabled.

Enabling channel hopping.

Enabling channel splitting.

Source 0 (Atheros): Enabling monitor mode for madwifi_g source interface wifi0 channel 6...

WARNING: Found a non-monitor VAP wifi0::ath0. Madwifi-ng has historically had problems with normal-mo
de VAPs combined with monitor-mode VAPs. Kismet has been configured to NOT destroy VAPs. To automatic
ally destroy non-rfmon VAPs, set vapdestroy=true in kismet.conf. Kismet likely WILL NOT WORK with non-
rfmon VAPs running.

NOTICE: Created Madwifi-NG RFMON VAP kis0

WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems i
n monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try
the latest versions of Madwifi-NG and remove other VAPs

Source 0 (Atheros): Opening madwifi_g source interface kis0...

Source 1 (Atheros): Enabling monitor mode for madwifi_g source interface wifi0 channel 6...

WARNING: Found a non-monitor VAP wifi0::ath0. Madwifi-ng has historically had problems with normal-mo
de VAPs combined with monitor-mode VAPs. Kismet has been configured to NOT destroy VAPs. To automatic
ally destroy non-rfmon VAPs, set vapdestroy=true in kismet.conf. Kismet likely WILL NOT WORK with non-
rfmon VAPs running.

NOTICE: Found existing monitor mode vap wifi0::kis0, Kismet will use that instead of creating its own
VAP

WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems i
n monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try
the latest versions of Madwifi-NG and remove other VAPs

Source 1 (Atheros): Opening madwifi_g source interface kis0...

Allowing clients to fetch WEP keys.

Logging networks to Kismet-Nov-15-2007-1.network

Logging networks in CSV format to Kismet-Nov-15-2007-1.csv

Logging networks in XML format to Kismet-Nov-15-2007-1.xml

Logging cryptographically weak packets to Kismet-Nov-15-2007-1.weak

Logging cisco product information to Kismet-Nov-15-2007-1.cisco

Logging gps coordinates to Kismet-Nov-15-2007-1.gps

Logging data to Kismet-Nov-15-2007-1.dump

Writing data files to disk every 300 seconds.

Mangling encrypted and fuzzy data packets.

Tracking probe responses and associating probe networks.

Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf

Reading client manufacturer data and defaults from /usr/local/etc/client_manuf

Using network-classifier based data encryption detection

Not tracking duplicate IVs

Dump file format: wiretap (local code) dump

Crypt file format: airsnort (weak packet) dump

Kismet 2007.10.R1 (Kismet)

Logging data networks CSV XML weak cisco gps

GPSD cannot connect: Connection refused

Listening on port 2501.

Allowing connections from 127.0.0.1/255.255.255.255

Registering builtin client/server protocols...

Registering requested alerts...

Registering builtin timer events...

Gathering packets...

Launching kismet_client: /usr/local/bin/kismet_client

Launched client, pid 3620

Looking for startup info from localhost:2501..... found.

Connected to Kismet server 2007.10.R1 on localhost:2501

Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf

Reading client manufacturer data and defaults from /usr/local/etc/client_manuf

Didn't see any weak encryption packets, unlinking weak file

WARNING: Sometimes cards don't always come out of monitor mode

cleanly. If your card is not fully working, you may need to

restart or reconfigure it for normal operation.

Kismet exiting.

Done.



thank you for taking the time to read this

racelife


Reply to this message