Kismet Wireless

Kismet Forums

 

Posted by:skan
Subject:I can't get kismet to run
Date:14:48:47 10/01/2008

Hello.
I need some help.

I'm trying to use kismet on Mandriva 2008 with my Atheros.
After trying different madwifi and aircrack patches I've found that madwifi-0.9.3.2-3mdv2008.0.rpm can be patched for reinjection on my system(all installation messages were OK).
Last year I was using Mandriva 2005 and old versions of madwifi and kismet and I was able to use kismet without any problem, but now...
I can connect to my AP but I'm not able to use kismet:


su -
ifconfig
(xxx means personal data)

ath0 Link encap:Ethernet HWaddr xxx
inet addr:xxx Bcast:xxx Mask:255.255.255.0
inet6 addr: fe80::xxx Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6270 (6.1 KiB) TX bytes:10099 (9.8 KiB)

kis1 Link encap:UNSPEC HWaddr 00-xxx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6814 errors:0 dropped:0 overruns:0 frame:986
TX packets:149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:568914 (555.5 KiB) TX bytes:15445 (15.0 KiB)
Interrupt:20

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)




iwconfig

lo no wireless extensions.

kis1 no wireless extensions.

ath0 IEEE 802.11g ESSID:"xxx" Nickname:"localhost"
Mode:Managed Frequency:2.437 GHz Access Point: 00:xxx
Bit Rate:36 Mb/s Tx-Power:18 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:xxx Security mode:open
Power Management:off
Link Quality=18/70 Signal level=-77 dBm Noise level=-95 dBm
Rx invalid nwid:3374 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0






I've tried to solve the problem:


airmon-ng start ath0 (same with airmon-ng start wifi0)

Interface Chipset Driver

kis1 Atheros madwifi-ng
ath0 Atheros madwifi-ng VAP (parent: kis1) (VAP cannot be put in monitor mode)




kismet (with source=madwifi_ag,wifi0,Atheros,5)
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to juanjin (500) gid 500
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_ag source interface wifi0 channel 5...
debug - open failed: /sys/class/net/wifi0/device/ No such file or directory
FATAL: Unable to create VAP: No such device
FATAL: Unable to create monitor-mode VAP
WARNING: wifi0 appears to not accept the Madwifi-NG controls. Will attempt to configure it as a standard Madwifi-old interface. If you are using madwifi-ng, be sure to set the source interface to the wifiX control interface, NOT athX
FATAL: GetIFFlags: interface wifi0: No such device





kismet (with source=madwifi_ag,ath0,Atheros,5)
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to juanjin (500) gid 500
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_ag source interface ath0 channel 5...
WARNING: Could not get mode of vap ath0::kis1, skipping
FATAL: Unable to create VAP: Operation not supported
FATAL: Unable to create monitor-mode VAP
WARNING: ath0 appears to not accept the Madwifi-NG controls. Will attempt to configure it as a standard Madwifi-old interface. If you are using madwifi-ng, be sure to set the source interface to the wifiX control interface, NOT athX
FATAL: 'get_mode' does not return integer parameters.





kismet (with source=madwifi_ag,kis1,Atheros,5)
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to juanjin (500) gid 500
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_ag source interface kis1 channel 5...
WARNING: Found a non-master non-monitor VAP kis1::ath0. Madwifi-ng has historically had problems with normal-mode VAPs combined with monitor-mode VAPs. You may need to remove them.
NOTICE: Created Madwifi-NG RFMON VAP kis0
WARNING: kis1 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems in 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_ag source interface kis0...
Spawned channelc control process 9924
Dropped privs to juanjin (500) gid 500
Logging networks to Kismet-Jan-09-2008-1.network
Logging networks in CSV format to Kismet-Jan-09-2008-1.csv
Logging networks in XML format to Kismet-Jan-09-2008-1.xml
Logging cryptographically weak packets to Kismet-Jan-09-2008-1.weak
Logging cisco product information to Kismet-Jan-09-2008-1.cisco
Logging gps coordinates to Kismet-Jan-09-2008-1.gps
Logging data to Kismet-Jan-09-2008-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 /etc/ap_manuf
Reading client manufacturer data and defaults from /etc/client_manuf
Using network-classifier based data encryption detection
FATAL: Dump file error: Unable to open dump file Kismet-Jan-09-2008-1.dump (Permission denied)
Sending termination request to channel control child 9924...
Waiting for channel control child 9924 to exit...
Kismet exiting.




airmon-ng stop kis1


Interface Chipset Driver

kis1 Atheros madwifi-ngkis1 does not support 'stop', do it on ath interface



airmon-ng start kis1


Interface Chipset Driver

kis1 Atheros madwifi-ngError for wireless request "Set Frequency" (8B04) :
SET failed on device ath0 ; No such device.
ath0: unknown interface: No existe el dispositivo

ath0_re Unknown Unknown (MONITOR MODE NOT SUPPORTED)



I've also tried with source=madwifing_g and several other and It's the same.
I've also tried by using sudo on every command but it doesn't solve anything.

kis1 device was automatically created by kismet.
I've tried to remove kis1 device and creating a new one with
modprobe ath_pci autocreate=monitor
but the new one is automatically called kis1. I guess madwifi doesn't like that name.


Reply to this message