Search the Community
Showing results for tags 'Guide'.
Found 4 results
Hey I got myself a Bash Bunny. I bricked it by accident (who would do this on purpose?) and I cant get it to work again. I already tryed the Ultimate Unbricking Guide but it doesnt seem to function. If I'm doing something wrong please tell me. Thanks
I am completely and utterly disappointed. i have been searching for weeks to find out how to preform a arp-poising MITM attack to sniff plain text credentials, the best thing i could find was Responder. There is no guide on how to use this explicitly on the WiFi Pineapple. I have basically paid $250 for a box. The last person to ask about this did not get anywhere in terms of help either. Please Can somebody in this entire forum show me how i can configure Responder to work on a Wireless network. Like from the ground level. What options do i select, do i connect in client mode (Wlan1, Wlan0) ect. Please, this was a big investment for me.
What Golden Rules of set-up process' for your Pineapple Nano before doing what you do? It's taken me a few weeks to figure a couple things out. While it's neither amazing or extensive, it is something that works for me at my level. I would love to see a few steps that you take to get what you want out of the Nano. I hope this thread will turn into a good fresh-meat nano owner's thread to get their understanding feet wet. 1. This is a setup while stationary in town (ie park with kid, dinner, ect..). Generally I utilize PineAP, SiteSurvey, Recon, ngrep, Make sure logging is recorded to the SD card once an hour as the nano isn't running usually for more than 4 hours. Enable the PineAP, minus probe logging and broadcasting the SSID Pool. Turn the SSID broadcasting rate to minimum but turn the response to probing to aggressive. Set the WLAN2 to a working AP. Set ngrep (still don't fully understand what this does) to work on wlan0. Recon goes to work on a 5 minute scan. Sitesurvey to see if there's a common AP to death and capture. Then go about applying MAC tracking and deaths via recon window. I'll post another setup process after I refine my arcade button-mashing like nano use. I still have issues understanding which modules and interface initiations break other interface workings on other modules. For example: YOU CAN SiteSurvey with wlan1mon and it won't stop the PineAP from running. YOU CAN run ngrep on Wlan0 and not boot all your clientele. YOU CANNOT initiate sitesurvey with wlan0-mon without booting yourself (I think that's what I did to kick myself out of the administration SSID). What are some of the Golden Rules of 'use this with this but not with that'? EDIT: spotted this in the sitesurvey module thread: Running deauth mode for length consistently locks the pineapple up. The situation seems to be aggravated when recon wlan1 is active also, resulting in scans being dropped entirely and a situation where factory reset was needed to restore. Golden Rule: Don't run sitesurvey deauth while recon wlan1 is active. Good to know.
Hey folks, So I'm on an active gig and I have two turtles deployed at a client. I burned all of yesterday trying to follow a bunch of walkthroughs of how to get openvpn setup (I think I have the server mostly setup), so rather than burning any more days of this gig trying to get the client part on the turtle working, I was hoping to basically copypaste some sort of simple config from someone who already has it setup. If anybody has a quick, bullet-point list of the steps required that would be super useful. I fathom that in the future (the very near future) these steps could be rolled into a deployment shell script that would permit someone in a pentest/redteam role to rapidly deploy a brand new server on an ec2/digitalocean VM and quickly reconfigure the turtle - this is especially helpful if you end up playing cat-and-mouse with the blueteam and they find/block your hosts in a short turn around. Any help would be appreciated!