Jump to content

WatskeBart

Active Members
  • Posts

    239
  • Joined

  • Last visited

  • Days Won

    4

Profile Information

  • Gender
    Male
  • Location
    AMS-IX

Recent Profile Visitors

5,705 profile views

WatskeBart's Achievements

Newbie

Newbie (1/14)

  1. How clear does it need to be? Source: https://wiki.bashbunny.com/#!downloads.md
  2. Here are the MK5 GPIO's LED or DIP GPIO MK5_DIP_01 1 MK5_DIP_02 13 MK5_DIP_03 15 MK5_DIP_04 16 MK5_DIP_05 11 MK5_SD_01 23 MK5_GPIO_LED_01 27 MK5_GPIO_LED_02 14 MK5_GPIO_LED_03 17 MK5_GPIO_LED_POWER 0
  3. I'll check this out later. Thanks for the info 👍
  4. How did you flash the OpenWRT firmware? Because sysupgrade will throw a error when you try flashing anything other than a "official" firmware. Did you modify the MR3040 firmware or did you build from source?
  5. If you do want to start making your own de.json, look at this thread from @elkentaro
  6. Create your own and place in languages folder ;)
  7. You could try ATTACKMODE STORAGE as well. I should show up as a USB disk drive. Also have you tried another machine as well?
  8. Try creating a payload on switch 1 or 2 with the following text: ATTACKMODE SERIAL Then check if Windows assigns a COM port to the bunny. You can check with the device manager or with the following command in the command prompt: mode
  9. Which switch position are you talking about?
  10. @chairman glad it worked out. Interesting though why it wouldn't work on Win10 work laptop and if so which policy is preventing this.
  11. Is your payload.txt containing: ATTACKMODE RNDIS_ETHERNET? Is the BashBunny recognized as a IBM USB Remote NDIS network device? If so, does it get a IP e.g. 172.16.64.10 (use ipconfig /all you should see IBM USB Remote NDIS Network Device in the description)? Then you should be able to SSH into 172.16.64.1 and connect to the BashBunny This works for me, and i'm using a firewall as well.
  12. Look what @Cpt.Pickles posted here. This site tells it all.
  13. To get apt working, just follow this part on the wiki and then SSH into the BashBunny using PuTTy or KiTTy with IP 172.16.64.1 Works for me, as you can see: root@bunny:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=45 time=18.4 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=45 time=14.9 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=45 time=18.2 ms ^C --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 14.949/17.190/18.419/1.587 ms root@bunny:~# apt-get update Ign http://httpredir.debian.org jessie InRelease Hit http://httpredir.debian.org jessie Release.gpg Hit http://httpredir.debian.org jessie Release Hit http://httpredir.debian.org jessie/main armhf Packages Hit http://httpredir.debian.org jessie/main Translation-en Reading package lists... Done root@bunny:~#
  14. What kind of attacks are you thinking about? The device when powered runs a full debain distro, so it don't see any problem running things when powered by a battery.
×
×
  • Create New...