GermanNoob

OK, so let's start working on your issues... According the BashBunny: Why don't you install an virtual machine with Windows to test your payloads? I personally find that very useful, just to see if I messed up something before going to the real targets... Am I assuming right, that you own a WifiPineapple Nano AND a WifiPineappleTetra? I'm just confused as you are talking about Pineapple and Nano... I have a WiFiPineapple Nano, updated it to the actual software not long ago and I can assure you it works fine... To get more specific, I suggest you just open a thread in the right forum and explain what you are trying to achieve and which modules you are using. biggest problem for newcomers: Check your filter settings! Best regards!

@Pentester1975, I don't know which products apart from the Pineapple Nano you tried. But if you don't get them going you are probably a very poor pentester if at all... As you can see from the comments and the help of other users, the products work just fine. But unfortunately a lot of Skiddies are buying the stuff and think they are now hackers or pentesters. In many threads you will see, that people often don't understand the basics of networks, bash, etc. No product in the world will make you a pentester or hacker! You have to do it by yourself! By buying a formula 1 racing car you will not become a formula 1 driver. If you expected something else, it might be the best to ask Hak5 (in a kind manner) if they would take back your gadgets. And before the trolling starts: No, I'm not paid by Hak5, but I use several (not all) of their products...

Have you copied only the payload.txt from the library or everything within the tools_installer folder? You need to copy everything! I'm wondering what happens here... payload_installer does NOTHING on your host machine! Do you understand BASH scripts? Check the install.sh!

OK let's work on one... So what exactly did you do while trying tools_installer and what happened. Please describe step by step, as probably you will have done something wrong and we need to find our what...

@paimon Have you installed the actual GitHub version of the payloads? If yes, which payload are you trying to run? Which OS are you using?

Hi @My Name Jeff these are the steps for recovery: Switch to arming mode (Switch3 nearest to USB) Plug the BashBunny into USB or an an power source Wait until the GREEN LED turns off (roundabout 3 secs?) Unplug the BashBunny Repeat step 2 - 4 another two times (which means: create three fail boots) replug the BashBunny and wait! The BashBunny will blink RED for about three minutes. DON'T UNPLUG IT!!!! The BashBunny will reboot; You're fine to work with it, when it blinks BLUE again...

You're welcome, @GreenRubi

Have you downloaded the newest version of all payloads (including bunny_helpers.sh) from GitHub? try the test I just described and tell us the result.

That's really weird as I tested your first payload on my BashBunny & Computer and it works just fine... Have you tested the bunny_helpers.sh "offline" meaning without using in a payload? Just connect your Bunny and connect to it with screen or ssh Mount the payload drive to /root/udisk with mount -o sync /dev/nandf /root/udisk 3. goto /root/udisk/payloads/library 4. type "source bunny_helpers.sh" 5. type "echo $SWITCH_POSITION" That should work and tests your bunny_helpers.sh

Sorry, @trumpet7347! Obviously I didn't read your post correctly... Having a look again to your code the problem is the brackets: ${SWITCH_POSITION} just try this: QUACK STRING Testing Switch Position, Switch Position is $SWITCH_POSITION

You're welcome, @terrier

OK, then let's do it step by step: Switch to arming mode (Switch3 nearest to USB) Plug the BashBunny into USB or an an power source Wait until the GREEN LED turns off (roundabout 3 secs?) Unplug the BashBunny Repeat step 2 - 4 another two times (which means: create three fail boots) replug the BashBunny and wait! The BashBunny will blink RED for about three minutes. DON'T UNPLUG IT!!!! The BashBunny will reboot; You're fine to work with it, when it blinks BLUE again...

Tested it... Well it is: diskutil unmount /Volumes/BashBunny Works for me

Hmm, what do you not understand of the description I posted ?

I haven't tried it but probably you could do this with the terminal umount command...