WyldWolf

Awesome!

Sure will pull it and post. I just want to actually enable and use the WPA2 protected management AP on WLAN0-1 and even though it can be seen no matter what password is set, a client cannot successfully connect to it to manage the MKV. It attempts connection and fails almost as if the pwd is not being accepted. I tried multiple resets of the wifi to defaults and reboots of the MKV I'm just curious it seems most do not actually use it and since it looks like the WLAN0-1 is now a new feature of 2.11 whether people are successfully connecting and managing their MKV specifically on that secure AP.

Uncheck the "disabled" box for the "management" wlan0-1 and can ANYONE connect to wlan0-1?!? Becoming increasingly frusterated that this device at this revision level still seems like such a pain and so flaky. Can anyone confirm this works or whether it is, as I suspect, completely utterly broken in v2 of firmware? Even upon resetting all wireless to defaults bringing back default SSID's for AP.....if ALL I do is uncheck the disable box for mgmt and set a 8 char password and reboot sure enough I can see the SSID being broadcast, and no matter what I cannot connect to it successfully.

Latest v2 firmware MKV and man if this thing does not freeze up when trying to do scans using either built in radios or even the Alfa. I'm starting to wonder is this a hardware issue or a firmware issue? Is anyone else getting continual unresponsive need to pull AC power and restart their MKV? Aside from what could be a hw or firmware issue, I don't like giving up on things but I am starting to agree with others unless I have a bad unit are these really just tinker toys that really don't work as well as the few videos I've found? Has anyone else seen actual video of a pineapple performing a working end-to-end MITM attack? In the days I've spent screwing around with this pineapple, in a hour I spun up a kali VM and I can find literally dozens of videos of actual end-to-end MITM with backtrack and kali, only some brief vids w pineapple. The pineapple "university" is an awesome idea, but unfortunately does not have a single video showing a simple start to finish karma+dnsspoof as example, heck even karma+urlsnarf and with the client mode hardware bug taking that long to pinpoint I am just curious how many can raise their hands and say other than partial proof of concepts that their pineapple can actually perform a full penetration test using the infusions and GUI? I would love to see a single video of someone configuring their pineapple all the way to showing a victim computer compromised - maybe I'm just missing it when I search any help greatly appreciated and something I can compare step by step with my MKV and this Firmware version to see if perhaps I simply need to roll back firmware or ?

This was from August....? I agree some documentation on these features would be great - I also do not find any yet they are constantly referred to.

wlan1 is never enabled at boot, there is nothing "strange" about it many systems boot with one of mult interfaces down. WLAN1 is used for injection since the hardware bug identified in the MKV for client connectivity you should add a USB Alfa for WLAN2 and that, too will be disabled at boot. All of that can be changed via dip switch commands, etc. but I don't think it has anything to do with the firmware version you are using. My strong suggestion is to search the forum and do a bit more reading before freaking out too badly about what may be normal behavior and will help you learn (why we're here, right) pineapple usage a little more.

d3x, did you verify the default gateway is in fact now your client mode interface? Can you ssh to the MKV and from your terminal session verify IP routing thru wlan2?

Correction looks like I need a RP male to standard female which actually seems more common and really surprises me hakshop doesn't offer to allow the pigtails like yagi which are standard male to connect to the Alfa or booster which are RP female. Looks like this adapter will allow those antenna pigtails to connect directly to the Alfa or the booster: http://www.amazon.com/coaxial-coax-adapter-female-RP-SMA/dp/B00CVQ3XLY

So I ordered the MKV, the Omni and the yagi both of which have the standard SMA male connector. If I want to screw any external antenna with lead like this onto for instance the Alfa from hakshop which is a RP female SMA it looks like it would require a RP female SMA to standard female SMA. I'm surprised was the Alfa supposed to come with a pigtail for this purpose? I also purchased the booster which has an adapter but it's only for connecting to the pineapple and is a standard SMA male to RP female. So, in essence I'm trying to connect either the Omni or yagi to either the Alfa, or the booster and can't seem to do it with the one adapter and no pigtails provided. Right now the best I can do it take the Omni off the base go direct screwed onto Alfa (ugly and heavy) but no solution at all with the yagi. Does anyone have good experience with a particular source for the somewhat hard to find RP female to standard female adapter or pigtail, and/or is there a solution or part I didn't get etc that I'm missing to be able to do this?

Looks like it set 50% to swap with the mkfs.ext4 run so I missed that (BTW took 2 tries just for this card to be recognized after 1st boot/flash which makes me little nervous if I need to reflash. So, the big outstanding question is, @~6k each as example I want to install a dozen infusions to internal and have plenty left over and simply write those infusions to SD, can I symlink their log folders to SD, does anyone do this or am I alone in installing anything to internal? The vids I've seen always show "it's only 6k, so we'll install to internal"....but if after toggling sslstrip, urlsnarf, etc. on for couple runs and their log folders fill internal I'm wondering if anyone has perhaps written a nice shell script to symlink ALL the diff internally installed infusion's log/data folders to SD? If not, maybe I'll look at doing it but want to be sure I'm not reinventing the wheel!

I plan on replacing it what I asked was whether I got used or defective stuff with the card being in upon receipt against all the docs and vids I see, and a 2gb card that shows under 1gb after being formatted using web interface for short-term use with only the one ext4 partition in conjunction with the overall question of whether it is virtually NOT POSSIBLE to put a handful of these infusions into internal memory on the device because those infusions all write logs, etc. that cannot be easily redirected hence on a test run or two, the ~3mb free becomes zero so quickly it should simply be always the case (maybe forced in future) to only install to SD.

My question was whether they are shipping with the microsd also already inserted as mine was....everything I read says insert it but mine was in. Also, when I use web interface after initial boot/reboot and upgrade to 2.11 to format the SD, my df shows: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdcard/sd1 915116 29396 839836 3% /sd Is there a reason a microsd labeled 2g formatted with web interface only has a <1gig partition ext4 usable? It also appears nothing should really be installed to internal despite the tiny size like sslstrip because the logs cannot be redirected hence very quickly internal storage fills? Does everyone simply install all infusions to SD for this reason? I thought internal would be nice for small infusions and their configs and it would be easy to have them store their data to SD, but reading forums it's starting to look like that's really not the case? Thanks for the help!

New MKV holiday pack does not match video the microsd was already installed in unit no "firmware notes" card as shown in pineapple university unboxing vid so curious is this in fact a new unit, did the shipping change from the video? Also, the juicepack 1800 appeared fully charged I ran it with a 500ma 12v draw it lasted not quite an hour which seems defective to me it should be getting at least 6-8 hrs @ 500ma, correct? I am attempting one recharge then will RMA if necessary but hope it was a fluke.