danixdefcon5

I've had my MkV crash/reboot several times during my first 2 weeks monkeying around with the pineapple. I'm not sure exactly what causes it, but I do remember that I would crash it by running airodump-ng + at least 3 instances of aireplay-ng. I haven't had it crash for 3 weeks now, but I've changed a few things: I'm now using a Class 10 32GB microSD card. I've been using the 12V Pineapple Juice battery for those times when I'm doing heavy loads. Maybe it's rebooting because the I/O was choking?

Heh. I've done the warwalking thing recently by installing screen into the pineapple. Then I disable wlan0 (to allow channel skipping) and activate mon0 on the pineapple web interface, then ssh into the pineapple, start a screen session and run airodump-ng mon0 in there. Oh yes, remember to have everything stored into /sd, first time I did this I forgot changing dirs and filled up / real fast!

Happy Birthday Seb! :D

Did you check if the charger lit up the green light when charging? I found out that one of my outlets is faulty because the green light wouldn't come on, or would turn off after a couple of minutes.

Yes, you have to have the wlan2 interface down. Seems to be that while the interface is up, it gets locked.

Ooooh! I think the changes apply to the MKVs you were selling at DEFCON as well? The first time I was wading through the forums I read a lot about the update.bin thingy and I went "huh? I didn't have to do that!" and in fact one of the first things I did was to format the SD card. I prefer my filesystems open That said, I didn't fire up my MKV 'till I was back home, and basically set it up, formatted the SD card, and went straight to update it to 2.0.2. As much as I was itching to tinker with my pineapple during DEFCON, I was (rightly) paranoid about having it 0wn3d by the mystery pineapple hunter...

Thanks! I ended up buying an SDHC and as L0G1C says, the SDXC flavors are only available from 64GB and up, so the basic MKV specs hint me on SDHC anyway. Now I get fast I/O and more than enough storage for logs: Filesystem Size Used Available Use% Mounted on rootfs 3.6M 1.8M 1.8M 50% / /dev/root 11.5M 11.5M 0 100% /rom tmpfs 30.2M 2.5M 27.7M 8% /tmp tmpfs 512.0K 0 512.0K 0% /dev /dev/mtdblock3 3.6M 1.8M 1.8M 50% /overlay overlayfs:/overlay 3.6M 1.8M 1.8M 50% / /dev/sdcard/sd1 28.9G 913.7M 26.5G 3% /sd

Latest update: I finally was able to run bully. n00b mistake: I was having what is referred to as the "-1 channel bug" which happens when you enable monitor mode while having the associated wlan interface enabled. I disabled wlan2, started mon0 and voila! It works! Thanks, AlexJeb; yes it was wlan2 being enabled...

Can't remember if I did so, but I think I rebooted the Pineapple after formatting. Also, what firmware version are you using?

So, I've been reading about something called the SDXC SD cards. Haven't checked out if this format also exists for microSD, but I do read that it seems to be incompatible with SDHC or something like that. Do microSD SDXC cards exist? And if they do, does the Pineapple Mk. V support them? I'm going to buy a 32Gb Class10 microSD for my pineapple, but unsure if there are any incompatibilities due to the mysterious "SDXC" format.

wlan2 will appear, though it will be disabled by default. Use the Wi-Fi Manager infusion, it should show up there.

Doh! Post came out too late, you already answered the question. Oh well, I only got one Pineapple, but it sounds quite interesting. As it is, I'm using the ALFA radio plug so that I can have 3 radios available …

Which plug? Do you mean the Alfa adapter? I got the OTG kit which included that one :)

I'm actually using wlan2, which is a plugged-in USB ALFA radio adapter. I purposely set up mon0 on wlan2 to avoid getting the channel locked up into something else. I monkeyed around and set up mon1 on wlan1, as wlan1 was in connected to the target AP in client mode, so it made sense to try it this way. bully actually worked for a while, at least until the AP locked me out. Then after a couple of minutes it tried to switch channels and that's where it gave me the same message again. Maybe bully is trying to use an ioctl operation that isn't supported by the drivers?

I've been trying to run bully, but it just fails on me. I grabbed the command line generated by the wps infusion and I got this: root@Pineapple:~# bully mon0 -b 08:63:61:C3:D2:E4 -e "some_ssid" -c 11 [!] Bully v1.0-22 - WPS vulnerability assessment utility [+] Switching interface 'mon0' to channel '11' [!] ioctl(SIOCSIWFREQ) on 'mon0' failed with '-1' [X] Unable to set channel on 'mon0', exiting Maybe something missing in the kernel? "mon0" is a monitoring interface on wlan2 (the ALFA radio) but I've also got the same failure with mon0 on wlan0...