bobbytables

Thanks Sebkinne, instructions worked perfectly, I now have a working pineapple again!

After a failed or borked firmware upgrade using sysupgrade, the Mark V won't boot completely. Blue LED stays blinking, but network never comes up. So I switched the dip switches into "Recovery web interface", and I could access this interface, but I get an upgrade failed message immediately after hitting "flash" The firmware I'm using is from the Mark V download page: md5 upgrade.bin MD5 (upgrade.bin) = d9ca989ac9fa2855fbd38dcafee9c195

Hi, any update on how to unbrick a mark V? I performed a manual firmware upgrade using sysupgrade -n -v /tmp/upgrade.bin I'm sure I used the Mark V firmware, and I checked the md5sum before running that command. The device eventually went into blue blinking mode, at which point I unplugged, then plugged it in again. It blinked blue again and didn't stop, and I can't ping it's network interface, it just keeps blinking blue. EDIT: Then switched pin into "Recovery web interface", and I could access this interface, but I get an upgrade failed message immediately after hitting "flash" md5 upgrade.bin MD5 (upgrade.bin) = d9ca989ac9fa2855fbd38dcafee9c195

I've got to echo the original poster's sentiments. There are some assumptions I made when I bought the Mark V, that seem to have been wrong: - A new product is better than the older product - Infusions listed as available for the specific version I have, should work for that version - Buying a pineapple would involve less time on configuration than building one from scratch using an rPI or similar board. (This may still be true, but it's not as big a gap as I was expecting). - With dual radios, I can make a client connection to another AP. (Seems this may be possible with workarounds, which are documented in the forum somewhere). Sslstrip was a compelling reason to buy the pineapple, 'cause I wanted to use it in a demo for some students. If it's not working, then I would have liked to see a nice big warning sign on the online shop stating that. Similarly, if client connections don't work, that should be stated on the online shop. The primary value-add of the pineapple is its ease of use. Once it's start becoming less easy to use, then there's less of an incentive to buy it as opposed to an rPI + usb wifi and simply install the tools from scratch. Install-and-configure-everthing-on-the-commandline-without-any-documentation, was the step I was hoping to avoid with the pineapple.

Had the same issue. Thanks to leg3nd, sslstrip now starts up, but doesn't actually work. It's installed to internal mem. I've changed the default network and IP address of the pineapple to 192.168.2.1. Everything works fine on this address, can access internet, can run karma and clients connected through karma can access internet. So networking works. Installed firefox 16 on victim computer, which doesn't support HSTS just to be safe. Then browsed to www.yahoo.com (so searches are in clear text). Then searched for a site that I know offers SSL. Click on link, link takes me to the SSL version of the site. Then stopped sslstrip from the gui and ran it from the command line as follows: iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-port 9999 sslstrip -s -l 9999 Same behaviour. Any ideas?