Notices

Hi,

actually, if you are in red pill mode clicking the .deb-file in the file manage should fire up the application manager.
if you want to install it via the command-line become root and do a "dpkg -i foo.deb".

However, for kismet I would suggest tz1's build which is more recent than eko's build which bluesubaru mirrored. Just make sure to get the corrected *.conf-files for tz1's build (if I remember correctly I gave instructions for unpacking the .conf-files in posting #81 in this thread, the most recent .conf-files from me can be found in #91).

Thanks for the reply. I'm having a hard time finding tz1's build. Could you possibly point me in the right direction? I must be really dense, but I've looked through this thread multiple times, and the only link to the kismet app proper I found was the one bluesubaru posted (not counting the now defunct eko link).

Thanks again.

It was here
http://www.internettablettalk.com/fo...5&postcount=63

Unfortunately it is "before" bluesubaru's mirror of eko's build, but actually tz1's is more recent...

Do you have a bluetooth gps which you want to use with kismet? If so, use the first version of my configs (posting 81) and not the newer one.
The difference is that the older "#81" version waits for the gps to report a fix, the newer confs don't; the reason was that the n810's built in gps doesn't report any fix at all. But chances are good that an external bt gps behaves correctly and so waiting for a fix would be reasonable.

Thanks again. No I do not yet have a gps module, but I intend to get one. So I guess I'll go with the earlier configs.

According to tz1's post, I need to install tcpdump. Any idea where I can find that? I'm not getting any love from tcpdump.org.

Many, many thanks.

You can look for it here http://gronmayer.com/it/index.php?lang=en
Just make sure to select the correct OS Version before you use it.
The site also allows you to add all repositories currently available which is very helpful... Actually I use the application manager to look for new stuff now and then ;-)

Ok Tantris, I followed the directions you specified in post 81, using the frst config file. I think I'm close to getting it working, but I got the following error msg:

/home/user # kismet
Launching kismet_server: /usr/bin/kismet_s erver
Will drop privs to user (29999) gid 29999
No specific sources given to be enabled, a ll 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 i nterface wlan0...
Spawned channel control process 2186
Dropped privs to user (29999) gid 29999
Allowing clients to fetch WEP keys.
configdir '/home/user/.kismet/' does not e xist, making it.
SSID cloak file did not exist, it will be created.
IP track file did not exist, it will be cr eated.
Logging networks to /media/mmc1/Kismet-Mar -29-2008-1.network
Logging networks in CSV format to /media/m mc1/Kismet-Mar-29-2008-1.csv
Logging networks in XML format to /media/m mc1/Kismet-Mar-29-2008-1.xml
Logging cryptographically weak packets to /media/mmc1/Kismet-Mar-29-2008-1.weak
Logging cisco product information to /medi a/mmc1/Kismet-Mar-29-2008-1.cisco
Logging gps coordinates to /media/mmc1/Kis met-Mar-29-2008-1.gps
Logging data to /media/mmc1/Kismet-Mar-29- 2008-1.dump
Writing data files to disk every 300 secon ds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating p robe networks.
Reading AP manufacturer data and defaults from /usr/etc/ap_manuf
Reading client manufacturer data and defau lts from /usr/etc/client_manuf
Using network-classifier based data encryp tion detection
Not tracking duplicate IVs
Dump file format: wiretap (local code) dum p
Crypt file format: airsnort (weak packet) dump
Kismet 2007.10.R1 (Kismet)
Logging data networks CSV XML weak cisco g ps
GPSD cannot connect: Connection refused
Listening on port 2501.
Allowing connections from 127.0.0.1/255.25 5.255.255
Registering builtin client/server protocol s...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Launching kismet_client: /usr/bin/kismet_c lient
Launched client, pid 2187
NOTICE: configdir '/root/.kismet/' does no t exist, making it.
NOTICE: Group file did not exist, it will be created.
Looking for startup info from localhost:25 01..... found.
Connected to Kismet server 2007.10.R1 on l ocalhost:2501
Reading AP manufacturer data and defaults from /usr/etc/ap_manuf
Reading client manufacturer data and defau lts from /usr/etc/client_manuf
Error opening terminal: xterm.
Didn't see any weak encryption packets, un linking weak file
Sending termination request to channel con trol child 2186...
Waiting for channel control child 2186 to exit...
WARNING: Error disabling monitor mode: mod e set ioctl failed 22:Invalid argument
WARNING: wlan (wlan0) left in an unknown s tate. You may need to manually
restart or reconfigure it for nor mal operation.
WARNING: Sometimes cards don't always come out of monitor mode
cleanly. If your card is not ful ly working, you may need to
restart or reconfigure it for nor mal operation.
Kismet exiting.
Done.
/home/user #

Any idea what I've done wrong?

And thanks so much for all the info!

Hmm sadly I can't say what the reason is - and I only have experience with the n810.
The first evil line here is the
Error opening terminal: xterm

The strange thing is that the xterm application is not called xterm but osso-xterm...
Unfortunately I can't say why it "wants" to open something called "xterm"... The "Error"s later are normal, so I guess it's all about the xterm-line.

Did you install ncurses-base? But I think you've got to have it installed for installing kismet...

Maybe some other n800 users could give some advice?

/EDIT seems to be curses related, when I searched the forum for the xterm-line I found some stuff which was also ncurses-related. Get the packages libncurses and ncurses-base...

http://www.zdez.org/nokismet-0.0.1a.deb - the deluxe version with updated .conf files and sound support (sox included).

Note the built-in GPS does give fix information, but it must be turned on manually (or use a map). My zmapper application does this when it starts up. But using just the n810 with zmapper running, I got GPS positions in the log. If I have time this weekend it will also annotate channel information (it should work if there was signal strength to be had).

Great, tz1, will try it tomorrow, err, today...
This gps-fix-thing is strange as I started my gps by firing up maemo mapper and nevertheless the gps log was empty until I told kismet to ignore the fix information.
Of course the n810's gps *can* report a fix and in maemo mapper I can see whether there is one or not... In the last days I played around with (lib)gpsbt in python and while I could start and stop the gps and get the position, it always said "no fix"... is there some special way to check for a fix?

I think you also need libncurses, which I don't have as a dependency.

If you can launch kismet_server alone, that is likely the problem.