Jump to content

harmless

Active Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

391 profile views

harmless's Achievements

Newbie

Newbie (1/14)

  1. Hey, whether you know it or not, I think you're answering your own question here: It looks like your kali vm does not have any connection to the pineapple as currently configured. Assuming your eth0 is routed to the internet already, create another virtual adapter and bridge it to your mac's en0. After that, you should have the answer to the two confusing questions in the wp5.sh helper script: Interface between PC and Pineapple: eth0 ----> eth1 (The bridged adapter you just created) Interface between PC and Internet: wlan0 ----> eth0 (Kali's NAT connection to the internet) Does that help?
  2. Thanks for the suggestion Seb. I'm sure my oversight there would have prolonged my misery even more than it has lasted, but that wasn't the only problem. In case someone else runs into this issue, here's what I ultimately did to get kismet-server to run from a boot mode script: Since the list of commands I wanted to try was getting long, I decided to switch to using a shell script instead of dropping a list of commands in the web interface, not strictly necessary to the solution, but definitely easier on the eyes. The boot mode dialogue now says: logger "Boot Mode 110 executing now..."; /sd/scripts/boot110.sh & After installing coreutils-printenv, I was able to see that the collections of environment variables available to the various command environments (boot modes, 'execute command', and SSH) were hugely different. Further guesswork led me to believe I needed to set the PATH and LD_LIBRARY_PATH vars in my script so that kismet_server would be able to find everything it needed. Holy shit, it worked! Here is what that script looks like: #!/bin/sh #/sd/usr/bin/printenv >> /sd/var/log/boot110.log #Setting some environment variables so that kismet can run #These were copied verbatim from the SSH printenv output: export LD_LIBRARY_PATH='/lib:/usr/lib:/sd/lib:/sd/usr/lib' export PATH='/bin:/sbin:/usr/bin:/usr/sbin:/sd/usr/bin:/sd/usr/sbin' #Run kismet (daemonized to suppress unnecessary output): kismet_server --daemonize pineapple notify 'kismet now running' There were a couple of other tweeks necessary to get this to run off of the SD card, but this was the tough part. Thanks for all the help folks! I'm looking forward to some fun times with my pineapple. harmless
  3. OK, so this is something of a continuation of this thread: https://forums.hak5.org/index.php?/topic/32535-wardrive/page-2?hl=kismet Since the topic changed a bit, and it's a little stale, I thought I'd start a new thread. Here goes: So, just as @barry99705 said, kismet_server will not run from one of the boot mode command lines or from the 'execute command' window under settings > advanced in the pinapple web interface, but if I SSH into the pineapple and issue the command, it works as expected. Here is my boot mode command: logger "Boot Mode 100 executing now..."; logger "Starting kismet_server..."; kismet_server And here is the relevant log output (with a couple of extra lines for context): Jan 1 00:00:08 Pineapple daemon.info dnsmasq-dhcp[1833]: DHCPACK(br-lan) [removed] Jan 1 00:00:08 Pineapple daemon.info dnsmasq-dhcp[1833]: DHCPREQUEST(br-lan) [removed] Jan 1 00:00:02 Pineapple user.info sysinit: /bin/sh: kismet_server: not found Jan 1 00:00:02 Pineapple user.notice root: Starting kismet_server... Jan 1 00:00:02 Pineapple user.notice root: Boot Mode 100 executing now... Jan 1 00:00:00 Pineapple user.info sysinit: Wed Jan 1 00:00:00 GMT 2014 Also, for grins, I tried the full path to the command in case PATH variables weren't quite loaded yet (I'm running kismet from my sd card.): logger "Boot Mode 100 executing now..."; logger "Starting kismet_server..."; /sd/usr/bin/kismet_server Resulting in a slightly more curoius error loading libcap.so.2: Jan 1 00:00:03 Pineapple daemon.info dnsmasq-dhcp[1833]: DHCPACK(br-lan) [removed] Jan 1 00:00:03 Pineapple daemon.info dnsmasq-dhcp[1833]: DHCPREQUEST(br-lan) [removed] Jan 1 00:00:02 Pineapple user.info sysinit: /sd/usr/bin/kismet_server: can't load library 'libcap.so.2' Jan 1 00:00:02 Pineapple user.notice root: Starting kismet_server... Jan 1 00:00:02 Pineapple user.notice root: Boot Mode 100 executing now... Jan 1 00:00:00 Pineapple user.info sysinit: Wed Jan 1 00:00:00 GMT 2014 The only other thing I could think of to do, again in case environment variables needed time to load, was delay the command execution via sleep ala: sleep 30 && /sd/usr/bin/kismet_server with the same results in the logs only delayed a bit. Any other ideas on how to get kismet to autorun at boot? This is my first attempt at doing anything interesting with the pineapple, and I don't want to give up until it works. Thanks!
  4. Thanks. A reformat took care of it. Funny the things we don't try when troubleshooting sometimes.
  5. Hi all, New kid here. I'm having a problem saving infusions to SD. The Pineapple Bar doesn't seem to offer me the option like I've seen in some screenshots here in the forum. Whenever I try to install an infusion, I only get the "Install to internal storage" option in the popup. No mention of storing to SD. My firmware is 2.0.4 (flashed today). I have replaced the factory SD card with a new class 10 SD and formatted it using the "USB Info" tab on the Resources Infusion. I can verify that the /sd directory is in fact mounted on the Pineapple via SSH, and I even created a new directory in there for grins. Is there a conf file I need to edit? Any other possibilities? Thanks, harmless
×
×
  • Create New...