Dice Posted April 14, 2017 Share Posted April 14, 2017 Not getting it : I have set the attackmode to ATTACKMODE RNDIS_ETHERNET Selected that switch :) I share my Wifi connection The connection is enabled; IP set to 172.16.64.64 / 255.255.0.0 Yet : when i try to ssh into the BB : i get 'Connection Refused OS : Windows 10 Enterprise / 16 Gb / Inten Dual Band Wificonnector Link to comment Share on other sites More sharing options...
Dice Posted April 15, 2017 Share Posted April 15, 2017 On 4/14/2017 at 3:19 PM, Dice said: Not getting it : I have set the attackmode to ATTACKMODE RNDIS_ETHERNET Selected that switch :) I share my Wifi connection The connection is enabled; IP set to 172.16.64.64 / 255.255.0.0 Yet : when i try to ssh into the BB : i get 'Connection Refused D OS : Windows 10 Enterprise / 16 Gb / Inten Dual Band Wificonnector Disregard this; I was trying to connect to the wrong end of the BashBunny; Appartently the 'attack-side' of the ethernet connection does allow ssh traffic ... My bad Link to comment Share on other sites More sharing options...
Fang_Shadow Posted April 16, 2017 Share Posted April 16, 2017 Subnet is 255.255.255.0 for the BB Link to comment Share on other sites More sharing options...
Dice Posted April 16, 2017 Share Posted April 16, 2017 6 hours ago, Fang_Shadow said: Subnet is 255.255.255.0 for the BB Without a default gateway that does not matter; The only difference on this subnet set it expects 65534 hosts to be available on the local subnet before moving packets onto the default gateway. However my mistake was different; I set the IP to 172.16.64.64 manually and expected that side of the BB to answer to SSH commands. If i hadnt set that IP it would have gotten an IP from the internal DHCP server and been given a different Ip address. (172.16.64.10-12) the SSH commands are meant to be started from the 172.16.64.1 IP. Link to comment Share on other sites More sharing options...
super-6-1 Posted June 1, 2017 Share Posted June 1, 2017 I know this is a old post. Instead of making a new one i figured i post here. The issue i have is everything is set up via wiki, i can ping to it from the windows machine but not from the BB every time i ping it never times out but it will keep going forever till i do. I can even SSH into it with no issue. Any idea? im using switch two. Link to comment Share on other sites More sharing options...
Dave-ee Jones Posted June 2, 2017 Share Posted June 2, 2017 23 hours ago, super-6-1 said: I know this is a old post. Instead of making a new one i figured i post here. The issue i have is everything is set up via wiki, i can ping to it from the windows machine but not from the BB every time i ping it never times out but it will keep going forever till i do. I can even SSH into it with no issue. Any idea? im using switch two. What are you trying to ping? If you are trying to ping the BB it won't work very well because the BB is configured to ignore pings. Darren showed us how to make it respond to pings by using this command: echo "0" > /proc/sys/net/ipv4/icmp_echo_ignore_all (Well, I believe that is what it does anyway. @Darren Kitchen or @Sebkinne, can you confirm?) And you probably would have been better off with a new post instead of hiding out in an older one :P Just a suggestion. Link to comment Share on other sites More sharing options...
Dystrakti0n Posted June 18, 2017 Share Posted June 18, 2017 On 5/31/2017 at 9:52 PM, super-6-1 said: I know this is a old post. Instead of making a new one i figured i post here. The issue i have is everything is set up via wiki, i can ping to it from the windows machine but not from the BB every time i ping it never times out but it will keep going forever till i do. I can even SSH into it with no issue. Any idea? im using switch two. To clarify, you can SSH in, but are not getting an internet connection while SSH'd into the BB? Link to comment Share on other sites More sharing options...
ccollins Posted July 9, 2017 Share Posted July 9, 2017 IT WORKS! For anyone else still struggling with this problem here's how I fixed it. Note: I'm running Windows 10 and sharing connection from Ethernet 1 (windows NIC) to Ethernet 4 (BashBunny NIC). I basically had to reset the network sharing by doing this, Press [WindowsKey]+[r] and type "ncpa.cpl" Right click the Windows NIC (Ethernet 1 in my case) and select properties Click the "sharing" tab Uncheck both boxes and click "ok" Disable all network cards by right clicking and selecting disable....after a second or two re-enable the Network cards. Right click the Windows NIC (Ethernet 1 in my case) and select properties Click the "sharing" tab Check the first checkbox saying "Allow other network users to connect through this computer's Internet connection" In the text box type or select the dropdown for your BashBunny network ("Ethernet 4" in my case). Click ok Right click your BashBunny NIC (Ethernet 4 in my case) and select properties. Select "Internet Protocol Version 4 (TCP/IPv4)" and click properties. You'll see some random ip address here. Enter the ip: 172.16.64.64 and subnet: 255.255.255.0 and leave the rest blank. Click Ok..and Ok again. SSH into your BashBunny and try pinging google (type: ping google.com) and it should work. Link to comment Share on other sites More sharing options...
oat Posted July 22, 2017 Share Posted July 22, 2017 Quick Note, do NOT use the set your Windows BashBunny Nework interface to use the DHCP option from BashBunny! It will put a gateway in for you of 172.16.64.1 (BashBunny IP) and then you will have 2 gateways on Windows which messes up your internet traffic because it conflicts with your main NIC that points towards Internet. Now you can't get to the internet. I'm sure that's why a few of the people couldn't get ICS to work. Setup the BB Windows Adapter to be 172.16.64.64/24 (as the document says) and leave DNS and gateways entries BLANK in Windows. BashBunny's linux distro has the gateway it should route out of as 172.16.64.64, which is why the document specifically tells you to set YOUR WINDOWS BashBunny Adapter to that specific IP. If you change your NIC IP, then you need to change the default route in BB Linux. BB routes to that NIC, then out through the one you set up for ICS. Link to comment Share on other sites More sharing options...
nmery Posted September 10, 2019 Share Posted September 10, 2019 And if you happen to use a firewall like McAfee be sure to add the network range as Home. Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 10, 2019 Share Posted September 10, 2019 On 4/13/2017 at 12:58 PM, devildog31415 said: what doesn't work is apt-get update.. it just times out. Need to post the output of this. Are you sure your repos are correct for apt update? You seem to have a good network connection from your post. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.