Search the Community

Hello, I'm a frequent wardriver (Walker actually, whenever possible.) and I like the new size of the Nano, so I was thinking about using it to do the job. I usually use the Wiggle app, but this drains my battery pretty quickly. The only thing I need to make this work is a GPS that works with any program I could use for this. (For example I've read a lot about using Kismet with a GPS) Are there any GPS units that both work with the pineapple, and are small enough to reasonably attach to the Nanos tactical case? Here is a picture for size. Take from another post.

tl;dr: I've had a couple instances of my WarWalking data being corrupted when shutting off the Pineapple at the end of a session. Any suggestions for a method to cleanly shut down the Mark V without having to SSH in and type commands? For example, I believe the DIP switches are currently only read at power-up; maybe there's a way to configure one of them to generate a GPIO interrupt and have the interrupt handler signal a shutdown script? Full Story: I purchased the "Tactical Bundle" a while back and have been using it, along with the awesome GlobalSat BU-353S4 USB GPS puck, to do a little WarWalking. I ran into some problems along the way and thought I would share my solutions here in case others are having the same issues. Problem: I wanted to capture using both radios for fewer missed packets. Kismet supports this and will automatically coordinate the channels on each radio so that each one is always listening to a different channel. Solution: Kill hostapd process and put both radios into monitor mode. Problem: I wanted to auto-start in WarWalking mode at powerup, so I don't have to SSH in to type commands or start anything manually. Solution: Configure the DIP swiches to run a script (attached below). Problem: Pineapple has no RTC, so when it boots up without a network connection the NTP daemon cannot set the clock. This results in all the Kismet output files having the same "January 1st" date. Solution: Get the time from the GPS data stream. In my startup script I added a few lines to 1) Wait for gpsd to acquire a 3D satellite lock, and 2) to parse the output of gpsd for the time and use that info to set the system clock. Problem: Heat buildup inside the messenger bag. The Tactical Bundle comes with a very nice bag, but it has zero airflow through the interior, and the Pineapple runs a bit warm. Workaround: Limit duration of war walks. Most of mine last under an hour, so it hasn't really been an issue. Still, heat is the enemy of electronics' longevity, so I'd like to keep things as cool as possible. Solution: Different bag with better airflow. I've seen bags with mesh pockets on the outside which looks like they would have good airflow, but then the Pineapple is basically out in plain sight so stealth goes out the window. Plus there's no protection in case of a sudden rain shower or lawn sprinkler. Problem: Shutting down cleanly to avoid file corruption. I've discovered it's possible to have the Pineapple lose power just as Kismet is writing out its data files, resulting in a zero-length .netxml file and complete data loss. Don't ask me how I know this. Workaround: Upon returning home, plug into the network, SSH in and shut Kismet down manually. A bit of a pain, but it works. Solution: ??? Looking for ideas here! Here is my startup script that gets executed when the middle DIP switch is in the down position. #!/bin/bash # START CLEAN pkill hostapd pkill gpsd pkill kismet /sbin/ifconfig wlan0 down /sbin/ifconfig wlan1 down # START GPSD /usr/sbin/gpsd -n /dev/ttyUSB0 # WAIT UNTIL IT'S READY TO ACCEPT CLIENT CONNECTIONS sleep 1 # MONITOR GPS STATUS AND WAIT FOR SAT LOCK gpspipe -w | grep -qm 1 '"mode":3' # PARSE THE CURRENT UTC TIME FROM THE GPSD OUTPUT UTCDATE=`gpspipe -w | grep -m 1 "TPV" | sed -r 's/.*"time":"([^"]*)".*/\1/' | sed -e 's/^\(.\{10\}\)T\(.\{8\}\).*/\1 \2/'` # SET THE PINEAPPLE'S CLOCK date -u -s "$UTCDATE" # LAUNCH KISMET DAEMON /usr/sbin/iwconfig wlan0 mode Monitor /usr/sbin/iwconfig wlan1 mode Monitor /usr/bin/kismet_server --daemonize