Notices

The best you can probably do is the one I put together:

http://www.zdez.org/nokismet-0.0.1a.deb

There is no official binary. You won't need drivers. This should just work after you install it (and run kismet - I forget if root is needed, and there might be some conf file tricks but they would be in the threads).

Note you need to do minimally ifconfig wlan0 down / ifconfig wlan0 up after running kismet to restore things.

tz1, app manager gives an "unable to install nokismet incompatible application package" error when trying to install the deb you linked.

There is a details or something when it says that. What does it say is wrong?

btw tz1 i got the same error heres the log output
hildon-application-manager 2.0.2
/usr/bin/dpkg-deb -f '/media/mmc1/backups/instals/nokismet-0.0.1a.deb'
Package must have "Section: user/FOO" to be considered compatible.
FAILED: tcpdump

Hi;

Tz1; thanks for keeping an eye on this thread. I'm getting the same failure as Joe:

I've confirmed I have tcpdump installed.

Still a bit too green to help myself much here.

Thanks,

Steve

Here are my two cents, summary of kismet installation.
I reflashed my N810 (well, I had to...) and installed these packages:

- becomeroot
- flite
- nano
- wifiinfo
- wirelesstools

downloaded nokismet, than as root:
dpkg -i nokismet-0.0.1a.deb (ignoring errors)
apt-get -f install (repairs/ads libpcap0.8 and tcpdump which were missing)

copied the two config files posted in this thread to /usr/etc

kismet runs fine!

to reinable wlan after kismet use:
ifconfig wlan0 down
iwconfig wlan0 mode ad-hoc
ifconfig wlan0 up

rolfok!

U da man! ... and also everyone else, in this thread and elsewhere, who helped me.
"I stand on the shoulders of giants".

Your hint, combined with careful re-reading of the entire thread, has resulted in almost 100% sucess. I'm taking notes and will turn this all into a wiki 'noob kismet install'...



Installed, runs, just one minor error the first time I ran it:

FATAL: Dump file error: Unable to open dump file /media/mmc1/kismet/Kismet-Jun-24-2008-1.dump (No such file or directory)

I also noticed that it did not produce any of the output files, even though it claimed to be writing them. There was no /media/mmc1/kismet directory. So, I manually created it and tried again, and this time I was rewarded with the real time Kismet screen in xterm!

Here's the lines from xterm, from install, to running:

Nokia-N810-51-3:/media/mmc1/download# dpkg -i nokismet-0.0.1a.deb
Selecting previously deselected package nokismet.
(Reading database ... 19195 files and directories currently installed.)
Unpacking nokismet (from nokismet-0.0.1a.deb) ...
Setting up nokismet (0.0.1a) ...
Nokia-N810-51-3:/media/mmc1/download# cd /
Nokia-N810-51-3:/# kismet
Launching kismet_server: /usr/bin/kismet_server
Will drop privs to user (29999) gid 29999
Enabling GPS position lock override (broken GPS unit reports 0 always)
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.
Source 0 (wlan): Enabling monitor mode for nokia770 source interface wlan0 channel 6...
Source 0 (wlan): Opening nokia770 source interface wlan0...
Spawned channel control process 2195
Dropped privs to user (29999) gid 29999
Allowing clients to fetch WEP keys.
configdir '/home/user/.kismet/' does not exist, making it.
SSID cloak file did not exist, it will be created.
IP track file did not exist, it will be created.
Logging networks to /media/mmc1/kismet/Kismet-Jun-24-2008-1.network
Logging networks in CSV format to /media/mmc1/kismet/Kismet-Jun-24-2008-1.csv
Logging networks in XML format to /media/mmc1/kismet/Kismet-Jun-24-2008-1.xml
Logging cryptographically weak packets to /media/mmc1/kismet/Kismet-Jun-24-2008-1.weak
Logging cisco product information to /media/mmc1/kismet/Kismet-Jun-24-2008-1.cisco
Logging gps coordinates to /media/mmc1/kismet/Kismet-Jun-24-2008-1.gps
Logging data to /media/mmc1/kismet/Kismet-Jun-24-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 /usr/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/etc/client_manuf
Using network-classifier based data encryption detection
Not tracking duplicate IVs
FATAL: Dump file error: Unable to open dump file /media/mmc1/kismet/Kismet-Jun-24-2008-1.dump (No such file or directory)
Sending termination request to channel control child 2195...
Waiting for channel control child 2195 to exit...
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.
Nokia-N810-51-3:/#

Hi all Kismet people;

I'm making nice progress. Read the Kismet README, found some sites that have usage tips, and went through all the help screens and the conf files. Still have a few questions, though.

* Is the 'readme' the manual? No other docs seem to be available on the Kismet site. Would love to read and not have to bug ITT people.

* The Readme hints that the "!" and "." have something to do with decay, but not much detail is provided..


* I have an n810. The confs that came with tte .deb specify
, but the readme hints there is a driver for the n810 :

I tried , and , but those do not work - kismet complaind about 'no such driver' and would not run. The 770 drivers seem to work for the most part, but I'm curious about the error. Is that because the .deb was compiled with just the 770 driver?

* Signal strength is not reported. Is that correctable?

Sorry to shot gun all these questions, but I will put the answers in the wiki.

Thanks,

Steve

I flashed my n810 to Diablo today and got all my apps, including kismet, running again. I was hoping that kismet would be more stable, but before I could test, I noticed something odd.

Now, when I press r to pop-up the packet rate graph, nothing happens.

Anyone else running kismet under Diablo and having the same problem?

Thanks,

Steve

I noticed the same on my n800 running Diablo and Kismet. pressing 'r' has no reaction.