How to get a compatible USB GPS to work with Kismet.

[Barry]

https://docs.google.com/document/d/1...9mU/edit?hl=en

[TAPE]

Good info Barry, and much appreciated, however I have tried with what I have
and it is not recognized, perhaps include a bit on the use of gpsd just in case ?

Also in my case, teh ;

cat /dev/ttyUSB0

does not work / show any info.

However when starting gpsd kismet returns GPS info.

Is using gpsd a real bad thing ? I seem to get that idea from your posts.

[Barry]

Good info Barry, and much appreciated, however I have tried with what I have
and it is not recognized, perhaps include a bit on the use of gpsd just in case ?

Also in my case, teh ;

cat /dev/ttyUSB0

does not work / show any info.

However when starting gpsd kismet returns GPS info.

Is using gpsd a real bad thing ? I seem to get that idea from your posts.

It has been in the past. We had to use an older version of gpsd to get it to spit out usable data with Kismet. I may have missed a tag with the cat command, but usually I get data, sometimes it takes a minute or so for data to actually start flowing. A lot of us that were wardriving back when it was really cool, and running slackware, usually kept a version, I'm pretty sure it was 8.10 or something like that on a computer to compile in when needed. Thorn or theprez98 might be better able to answer this question though. I've actually not used gpsd in a couple years, so not sure if they've fixed the problems. If it works for you, cool, but keep an eye on it.

[parrotface]

I have got kismet working today both with gpsd and without gpsd, but I am using a blue tooth Holux gpslim device not a serial device.

[Thorn]

It has been in the past. We had to use an older version of gpsd to get it to spit out usable data with Kismet. I may have missed a tag with the cat command, but usually I get data, sometimes it takes a minute or so for data to actually start flowing. A lot of us that were wardriving back when it was really cool, and running slackware, usually kept a version, I'm pretty sure it was 8.10 or something like that on a computer to compile in when needed. Thorn or theprez98 might be better able to answer this question though. I've actually not used gpsd in a couple years, so not sure if they've fixed the problems. If it works for you, cool, but keep an eye on it.

Yeah, around 2003-2005, gpsd would completely munge the NMEA output and just would not play nice with kismet. IIRC, the development had forked for some reason circa 2003, and what ended up out in the "stable release" in the middle of the decade basically sucked donkey balls. It may have been fixed since then, but I keep a complied executable of the older version on a USB drive and just copy it over as needed.

[TAPE]

Barry, would you be willing to put up a quick how to on upgrading to the new Kismet ?

I tried to upgrade manually, all seemed to go OK, but in reality nothing has changed ... I must have
messed up *doh*

Would like to try the latest 2011 Kismet and not have to use gpsd.

[Barry]

I just get the latest and greatest this way.

svn co https://www.kismetwireless.net/code/svn/trunk kismet-devel

The rest is actually in the kismet readme.

3. Quick start

PLEASE read the full manual, but for the impatient, here is the BARE
MINIMUM needed to get Kismet working:

* Download Kismet from http://www.kismetwireless.net/download.shtml
* Run "./configure". Pay attention to the output! If Kismet cannot
find all the headers and libraries it needs, major functionality may
be missing. Most notably, compiling Kismet yourself will require
the development packages and headers, usually called foo-dev or
foo-devel.
* Make sure that all the functionality you need was enabled properly in
configure. Almost all users will need pcap and libnl support for
proper operation.
* Compile Kismet with "make".
* Install Kismet with either "make install" or "make suidinstall".
YOU MUST READ THE "SUID INSTALLATION & SECURITY" SECTION OF THE
README OR YOUR SYSTEM MAY BE INSECURE.
* If you have installed Kismet as suid-root, add your user to the
"kismet" group

I also remove kismet from backtrack before doing the above. That way you don't accidentally run the older version, it's not in the standard location in backtrack.

[TAPE]

it's not in the standard location in backtrack.

aaaaahhh ... now I followed all the info as in the readme, so think I was being too easy in thinking I could
then simply type

 
kismet

and be on my way..


thanks, will try harder

eeks gawd, running into some linux 101 problems..
when removing kismet, does the newly installed kismet work nice with kisgearth that you know of ?

[Barry]

aaaaahhh ... now I followed all the info as in the readme, so think I was being too easy in thinking I could
then simply type

 
kismet

and be on my way..


thanks, will try harder

eeks gawd, running into some linux 101 problems..
when removing kismet, does the newly installed kismet work nice with kisgearth that you know of ?

That, I'm not sure of. I've never use it.

[purehate]

Kismet-newcore is in backtrack and its also the same Kismet in /usr/bin. Its not the latest svn check out but it works fine. I just used it this week for a wireless assessment and used both my GPS devices with it. I do however start gpsd on its own like "gpsd -n -N -D 3 /dev/ttyAMC0" or USB0 depending on the device.