The Kismet Thread - Page 17 - maemo.org

kp4djt | # 161 | 2008-09-07, 05:56 | Report

Well, I got my N810 back, I had to power it down and remove the battery in order
to get normal operation back on the WiFi NIC. Kind of a pain, but worth it to have
Kismet on the box, just needed to figure out how to get regular communications
back.

Benson | # 162 | 2008-09-07, 06:34 | Report

Did you reboot it, or just shut it down and power it back up with the charger attached?

qwerty12 | # 163 | 2008-09-07, 07:41 | Report

I had to. Thanks to tz1 and the kismet team:

The packets! The time!

Last edited by qwerty12; 2008-09-07 at 07:47.

luca | # 164 | 2008-09-07, 11:27 | Report

maybe you should install wireless-tools and do an "iwconfig wlan0 mode managed"

luca | # 165 | 2008-09-07, 11:51 | Report

Originally Posted by luca View Post

maybe you should install wireless-tools and do an "iwconfig wlan0 mode managed"

mmh, it seems that kismet already puts the adapter in managed mode (btw, Q doesn't seem to close kismet properly, I had to kill -9 it) however a

Code:

ifconfig wlan0 down
/etc/init.d/wlancond restart
ifconfig wlan0 up

allowed me to reeconnect to the access point, no need to reboot.

walts | # 166 | 2008-09-07, 12:27 | Report

On my N800, I am running Kismet 2007.10.R1 which I installed from http://eko.one.pl/maemo, bora distribution. The OS version is 4.2008.30-2

It exits normally with Q and the wireless connection returns to normal. This is the first time I have seen this. With my prior installations (prior to the last re-flash to upgrade the OS) I had similar problems to what you are describing. Either using ifconfig as shown or shutting down wireless with the screen applet and restarting it again usually got it going again. I only remember once that I had to reboot, and that was after kismet froze up on me.

Walt

Dali | # 167 | 2008-09-08, 11:54 | Report

One must use commends to reset wlan properly:

MY_MAC="00:19:4F:AND:SO:ON"
sudo iwconfig wlan0 mode managed
sudo airmon-ng stop wlan0
sudo macchanger -m $MY_MAC wlan0

Last command used if one changes MAC before scanning, using:

sudo macchanger -r wlan0
sudo kismet

massIV | # 168 | 2008-10-06, 21:34 | Report

qwerty12: are you using 2008-05-R1_armel.deb? It seems to work for a few hours and then stops seeing traffic for me. thanks tz1.

Irongeek | # 169 | 2008-10-12, 01:14 | Report

Using the kismet_2008-05-R1_armel.deb mentioned earlier in this thread, what is the most straight forward way to get it using the GPS and saving data to the miniSD card?

Irongeek | # 170 | 2008-10-12, 11:22 | Report

ok, I enabled gps in kismet.conf, and get this:

Code:

~ $ kismet
Launching kismet_server: /usr/bin/kismet_server
Will drop privs to user (29999) gid 29999
Waiting for Hildon gps to enable...
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (wlan0): Enabling monitor mode for nokia8x0 source interface wlan0 channel 6...
INFO - Setting Nokia device to online/normal mode...
INFO - Waiting for normal mode... done
Source 0 (wlan0): Opening nokia8x0 source interface wlan0...
Spawned channel control process 1425
Dropped privs to user (29999) gid 29999
Will attempt to put networkmanager to sleep...
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Oct-12-2008-2.network
Logging networks in CSV format to Kismet-Oct-12-2008-2.csv
Logging networks in XML format to Kismet-Oct-12-2008-2.xml
Logging cryptographically weak packets to Kismet-Oct-12-2008-2.weak
Logging cisco product information to Kismet-Oct-12-2008-2.cisco
Logging gps coordinates to Kismet-Oct-12-2008-2.gpsLogging data to Kismet-Oct-12-2008-2.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/kismet/ap_manuf
Reading client manufacturer data and defaults from /etc/kismet/client_manuf
Using network-classifier based data encryption detection
Not tracking duplicate IVs
Putting networkmanager to sleep...
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2008.05.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.255Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Hildon BT failed: GPS API should be called as "user" and not as root

I read somewhere you have to patch Kismet to drop privileges to user, but I have know Idea how to do that. Any ideas?