Abhi09 Posted September 3, 2017 Posted September 3, 2017 Hello there, I was trying to make my BB online after upgrading it to latest firmware 1.3_264. I was doing this on debian based linux(KALI). I followed the instructions on wiki to download and run the script. After i am choosing guided or manual option it failed to detect my BB. Although i can access my BB through console and directory. I don't know what is the problem may be any issue regarding firmware. Quote root@ABHI:~/bash# sudo bash ./bb.sh _____ _____ _____ _____ _____ _____ _____ _____ __ __ (\___/) | __ || _ || __|| | | | __ || | || | || | || | | (='.'=) | __ -|| ||__ || | | __ -|| | || | | || | | ||_ _| (")_(") |_____||__|__||_____||__|__| |_____||_____||_|___||_|___| |_| Bash Bunny by Hak5 USB Attack/Automation Platform v1 Saved Settings: Share Internet connection from wlp58s0 to Bash Bunny at enx001122334455 through default gateway 10.73.31.1 [C]onnect using saved settings [G]uided setup (recommended) [M]anual setup [A]dvanced IP settings [Q]uit Step 1 of 3: Select Default Gateway Default gateway reported as 192.168.1.1 Use the above reported default gateway? [Y/n]? n default via 192.168.1.1 dev wlan0 proto static metric 600 172.16.12.0/24 dev vmnet8 proto kernel scope link src 172.16.12.1 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.7 metric 600 192.168.95.0/24 dev vmnet1 proto kernel scope link src 192.168.95.1 Specify the default gateway by IP address: 192.168.1.7 Step 2 of 3: Select Internet Interface Internet interface reported as wlan0 Use the above reported Internet interface? [Y/n]? y Step 3 of 3: Select Bash Bunny Interface Please connect the Bash Bunny to this computer. ................................................... ................................................... ................................................... ................................................... ................................................... ................................................... ................................................... How to fix this? Thank You Regards ABHI Quote
jermzz Posted September 3, 2017 Posted September 3, 2017 (edited) If you're connecting by serial then you're in arming mode which doesn't support Ethernet. Use one of the switches and set to Ethernet attack vector. Then you may run the bb.sh and ssh into your bunny. Took me a few min to figure this out as well. Edited September 3, 2017 by jermzz 1 Quote
Abhi09 Posted September 4, 2017 Author Posted September 4, 2017 Hello Jermzz, Thanks for the reply. I don't know much about BB so i am not confirm about this ETHERNET ATTACK VECTOR but if you asked me to do this: Quote ATTACKMODE RNDIS_ETHERNET RNDIS_SPEED_5000 So i tried this in both the switches(1&2) but it didn't work. Can you please tell me if i am doing wrong in detail? Thanks for your time and patience. Regards ABHI Quote
Dave-ee Jones Posted September 4, 2017 Posted September 4, 2017 Linux doesn't natively support RNDIS. You need to use ECM_ETHERNET instead of RNDIS_ETHERNET. I'm not sure if you can use ECM_SPEED or not, either. Explanation: RNDIS_ETHERNET is for Windows (and some Linux distro) drivers. ECM_ETHERNET is for Mac and most Linux distros (e.g. Kali). RNDIS_SPEED_5000 sets the speed of the ETHERNET port to 5mbps. This is so the Bunny isn't seen as the main source of network, allowing the PC to use the internet given to it by the other port it's using (Ethernet/WiFi), which should be more than 5mbps (e.g. 100mbps or 1000mbps - gigabit). 1 Quote
Abhi09 Posted September 6, 2017 Author Posted September 6, 2017 Thank you Dave, It worked. I should have read BB wiki or have referred any script carefully for the solution. Anyway thanks for the help. Now the problem is i am not able to connect to the BB through console in linux when i am booting the bash bunny with a payload.txt whereas it works fine in arming mode. It throws error like : NO SUCH FILE OR DIRECTORY . One last thing when BB get detected than i am not able to browse internet on my host os (KALI) . Whats your suggestion? Thanks in advance. Quote
Dave-ee Jones Posted September 6, 2017 Posted September 6, 2017 (edited) 13 hours ago, Abhi09 said: Thank you Dave, It worked. I should have read BB wiki or have referred any script carefully for the solution. Anyway thanks for the help. Now the problem is i am not able to connect to the BB through console in linux when i am booting the bash bunny with a payload.txt whereas it works fine in arming mode. It throws error like : NO SUCH FILE OR DIRECTORY . One last thing when BB get detected than i am not able to browse internet on my host os (KALI) . Whats your suggestion? Thanks in advance. Okay, the first problem is an easy fix. Arming mode has 2 ATTACKMODEs running (by default): SERIAL and STORAGE. The arming payload.txt I gave you has 2 as well, but they are: ECM_ETHERNET and STORAGE. So you can either add SERIAL: ATTACKMODE ECM_ETHERNET STORAGE SERIAL Or SSH into your Bunny instead of serialing into it (default IP of Bunny is 172.16.64.1), so connect to that via SSH/Screen/whatever-console-your-using-that's-not-serial. The second problem is interesting, as I know how to fix it with RNDIS (this is what RNDIS_SPEED_5000 was for), but I'm not sure about ECM. Maybe @Sebkinne can shed some light? Edited September 6, 2017 by Dave-ee Jones 1 Quote
Abhi09 Posted September 7, 2017 Author Posted September 7, 2017 Thanks again Dave, I was able to connect via SSH as well as by screen by this: Quote ATTACKMODE ECM_ETHERNET SERIAL On the other hand for second problem I messed up with the configuration of iptables. The default gateway was supposed to be 192.168.1.1 but by mistake i save the script with 192.168.1.7 which wasn't allowing me to make my BB online and at the same time my connection get halted on my host os too.Thanks a lot for your time and help. Quote
Dave-ee Jones Posted September 7, 2017 Posted September 7, 2017 No problem, glad to hear it all works fine now :) 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.