shadesoflight Posted March 18, 2017 Share Posted March 18, 2017 (edited) I'm on openSUSE Tumbleweed. The problem is that guided setup finishes fine, but "Connect" just stays at "detecting". I cannot ssh into 172.16.64.64 or 172.16.64.1 Edit: I _can_ ping 172.16.64.64 but I cannot connect to the internet with the bunny plugged in so I'm guessing internet is not quite shared yet. After guided setup, I have this in my bb.sh: bbver=1 sbunnynmask=255.255.255.0 sbunnynet=172.16.64.0/24 sbunnylan=enp0s20f0u6c2 sbunnywan=wlp4s0 sbunnygw=192.168.43.1 sbunnyhostip=172.16.64.64 sbunnyip=172.16.64.1 sfirsttime=0 The results of running "ip addr" is the following: _before_ plugging in the bunny: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:a7:a0:25:8f:dc brd ff:ff:ff:ff:ff:ff inet 192.168.43.20/24 brd 192.168.43.255 scope global dynamic wlp4s0 valid_lft 2866sec preferred_lft 2866sec inet6 fe80::96ba:2993:def5:6187/64 scope link valid_lft forever preferred_lft forever 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:5b:76:4d:d2:22 brd ff:ff:ff:ff:ff:ff inet 172.16.64.64/24 brd 172.16.64.255 scope global enp0s31f6 valid_lft forever preferred_lft forever _after_ plugging in the bunny: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:a7:a0:25:8f:dc brd ff:ff:ff:ff:ff:ff inet 192.168.43.20/24 brd 192.168.43.255 scope global dynamic wlp4s0 valid_lft 2824sec preferred_lft 2824sec inet6 fe80::96ba:2993:def5:6187/64 scope link valid_lft forever preferred_lft forever 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether c8:5b:76:4d:d2:22 brd ff:ff:ff:ff:ff:ff inet 172.16.64.64/24 brd 172.16.64.255 scope global enp0s31f6 valid_lft forever preferred_lft forever 28: enp0s20f0u6c2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff inet 172.16.64.64/24 brd 172.16.64.255 scope global enp0s20f0u6c2 valid_lft forever preferred_lft forever inet6 fe80::6450:292d:7ae8:4335/64 scope link valid_lft forever preferred_lft forever Edited March 18, 2017 by shadesoflight Quote Link to comment Share on other sites More sharing options...
shadesoflight Posted March 18, 2017 Author Share Posted March 18, 2017 Follow-up: I ran the command manually ifconfig enp0s20f0u6c2 172.16.64.64 netmask 255.255.255.0 up this results in the bunny at 172.16.64.64 -- but the ping command to check for it is pinging 172.16.64.1 (why?) changing the "bunnyip" to 172.16.64.64 allows the bunny to be detected -- I still can't ssh into it though Quote Link to comment Share on other sites More sharing options...
GermanNoob Posted March 18, 2017 Share Posted March 18, 2017 Which ATTACKMODE have you set? Bunny should be under 172.16.64.1 as it acts like DHCP server for your computer. Quote Link to comment Share on other sites More sharing options...
shadesoflight Posted March 19, 2017 Author Share Posted March 19, 2017 Using the top-most switch w/ the payload.txt from the github repo for that position (i.e. switch 1) LED R B ATTACKMODE ECM_ETHERNET STORAGE Quote Link to comment Share on other sites More sharing options...
shadesoflight Posted March 31, 2017 Author Share Posted March 31, 2017 ping Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted March 31, 2017 Share Posted March 31, 2017 On 3/19/2017 at 7:05 AM, shadesoflight said: changing the "bunnyip" to 172.16.64.64 allows the bunny to be detected -- I still can't ssh into it though That's because the Bash Bunny is at 172.16.64.1. Changing the IP to the one assigned to your machine will just mean that you are pinging yourself. As to why bb.sh doesn't work, can you post any output that the script may give you? Quote Link to comment Share on other sites More sharing options...
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.