[Cannot install gumf on kali linux.]

Did you run 'apt-get -f install' just like it's said in the log ? If not, you should try that.

[GPSD Problem]

Ok thanks.

[aireplay-ng deauth doesnt work as it should be]

Did you start airodump-ng before deauthing ? If not, try starting airodump-ng, and leave it running while you run aireplay-ng in another window. When a 4 way handshake is captured, airodump will normally tell you in the upper right-hand corner, unless you're using a REALLY old version. You can see an example in this image (not mine) : http://s94.photobucket.com/user/TAPE_RULEZ/media/ocl03.jpg.html

[GPSD Problem]

Kismet most likely cleanly fails once the power is cut, as it directly talks to the device.

In that case, I would definitely use kismet directly.

Best Regards,

Sebkinne

Without GPSD and without ssh'ing in to kill it ?

[GPSD Problem]

Okay, got unlazy. We're running a newcore based kismet, so we really don't need gpsd. It can read serial devices without it. Here is the default gps part of the kismet.conf file.

# Do we have a GPS?
gps=true
# Do we use a locally serial attached GPS, or use a gpsd server?
# (Pick only one)
gpstype=gpsd
# gpstype=serial
# What serial device do we look for the GPS on?
gpsdevice=/dev/rfcomm0
# Host:port that GPSD is running on.  This can be localhost OR remote!
gpshost=localhost:2947
# Do we lock the mode?  This overrides coordinates of lock "0", which will
# generate some bad information until you get a GPS lock, but it will
# fix problems with GPS units with broken NMEA that report lock 0
gpsmodelock=false
# Do we try to reconnect if we lose our link to the GPS, or do we just
# let it die and be disabled?
gpsreconnect=true

This is what you need to change. Basically the gpstype= and the gpsdevice= lines. Forgot you can't change text color with the code tags... Damn, now I can't add a comment under this last code block... You're still going to need to ssh into the pineapple to shutdown kismet_server properly. Just pulling the plug will corrupt the current database.

# Do we have a GPS?
gps=true
# Do we use a locally serial attached GPS, or use a gpsd server?
# (Pick only one)
# gpstype=gpsd
gpstype=serial
# What serial device do we look for the GPS on?
gpsdevice=/dev/ttyUSB0
# Host:port that GPSD is running on.  This can be localhost OR remote!
gpshost=localhost:2947
# Do we lock the mode?  This overrides coordinates of lock "0", which will
# generate some bad information until you get a GPS lock, but it will
# fix problems with GPS units with broken NMEA that report lock 0
gpsmodelock=false
# Do we try to reconnect if we lose our link to the GPS, or do we just
# let it die and be disabled?
gpsreconnect=true

Thanks ! I'll try that too. Didn't really look that much into serial once I got GPSD working. You're right about not using GPSD: It just adds another thing that can fail... But do I just need to kill the process to shutdown kismet_server properly ? Or do I need to stay connected and do a ctrl+c to stop it ? (Sorry if I sound dumb, I'm pretty new at this )

[GPSD Problem]

Thanks ! I'll try that tonight.

[GPSD Problem]

Hi everyone !

So I recently bought myself a GlobalSat BU-353-S4 GPS reciever, to try wardriving/warwalking with the Mark V. I managed to make everything run fine by reseting the Pineapple, installing kismet-server and GPSD with OPKG, and customizing kismet.conf. To start GPSD up, I use this command:

gpsd -N -D5 /dev/ttyUSB0 -F /var/run/gpsd.soc

Then a LED started blinking on the GPS reciever, to show that everything is up and running. When I was done with my wardrive/warwalk, I simply powered off the Pineapple. The next day, when I powered the Pineapple back on, and ran the GPSD command, the LED on the reciever didn't blink (even after several minutes). The only way I found to make it all work again was to reset the Pineapple and then reinstalling everything, which is just too much pain to do everytime.

Am I missing something, like stopping GPSD before powering off ? Or is it just an error with GPSD ?

Thanks,

V3sth4cks153