Jump to content

Bob123

Active Members
  • Content Count

    83
  • Joined

  • Last visited

1 Follower

About Bob123

  • Rank
    Hak5 Fan ++

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So maybe not the exact answer your looking for, but you could always create the VM in virtual box and then convert it to proxmox. https://forum.proxmox.com/threads/migrating-virtualbox-vdi-to-proxmox-ve.9672/ But I'm with you, it'd be great to have a vanilla box and run a script on top of it to install everything. Maybe we can pick apart what they did?
  2. Hello. So a purchasing option for the Signal Owl is an Owl combo kit. What all comes with the kit? And more specifically what is the Essential Gear Wrap? Is it really just the little pouch you see in picture on it's page? I wasn't sure if it was just different wording cause originally I thought it meant essentials kit like the network kit or USB kit. I'm guessing that's not the case? Thanks.
  3. This may seem crazy but unplug it, remove the battery, and press the power button for at least two straight minutes. Coworker had a brand new laptop and the same thing happened. One day it just refused to turn on. I don't know if a capacitor holds a charge when it shouldn't or what the deal is. I never thought in a million years that trick would work but for whatever reason it did. Hope this helps.
  4. Can things go wrong? Sure. Can bad things jump from a vm to the main machine? I've heard it could happen. Have I ever had an issue with any of that? Absolutely not!!! This is what I do all the time. My main machine has 32GB memory and several hard drives. I spread the VMs over the multiple hard drives that way I can run several at a time. I think the most I've had running at once was 7 VMs. (That's right up there with my virtual server.) Trust me you don't want more than 2 VMs running on the same hard drive at the same time. Even the fasted SSD, it'll still be a bottleneck. But yes I highly recommend experimenting. I use both vmware and virtual box. If your going to use Kali and try to hack some VMs I'd recommend setting up a lan segment or have a third VM as a router. Don't use the 'host only', NAT, or bridged as they will open up the outside world. If you need to get some updates or software then sure use NAT but once your ready to hack keep it internal to the VMs.
  5. What was the boot setting you had to change?
  6. I think there is a minimum hard drive size for parrot and in this case almost all current Linux distros. I can't remember if it was parrot or a different one but I'd get almost through the install and it would give me a red screen with an error message saying install had failed. I just increased the hard drive size and it worked. These days with the size of hard drives I'd go with at least 30 to 50GB if you can. Side question for you, why dual boot? Honestly I've been doing this for a long long time and I've never seen a reason to dual boot. Would installing vmware or virtualbox on Windows 10 be an option? VMs these days are pretty robust and you can easily pass through USB, network, and pretty much anything else you'd need. I pretty much live by VMs. They are safe, you can take them anywhere, and if you break it you just open up a backup. Just my two cents.
  7. Forgive my ignorance and at the same time please educate me but my bash bunny is at firmware 1.3. If I wanted to go to firmware 1.5 can't I just load up the latest firmware into the BB? Do I have to do an apt-get update/upgrade? I'm curious cause looking at the most recent posts in the BB section of the forums, it seems that the update/upgrade is what's killing them. Is that correct to say? I'm currently trying to help someone else with quick creds and in determining if it's the BB or the win10 box, all things being equal, if I update the firmware from 1.3 to 1.5 then back to 1.3 my results should be the same with any script right? I started at 1.3 and the script worked, I upped the firmware to 1.5 then downgraded the firmware back to 1.3. Doing an apt-get update/upgrade is actually changing the underlying software that runs below the firmware correct? Again I'm just trying to wrap my head around this issue. Sorry for crashing this thread but you all seem to be the most active on working on this. Thanks.
  8. What version of win10 are you using? I want to test this. I will also test this with my wifi on because in all honesty I had my box isolated just because I saw no reason for it to be on a network at the time. So maybe I will then have issues as well. But I do like what PoSHMagiC0de said above. Try running the bash bunny with just an RNDIS network and see how Win10 reacts. I guess now with both wifi on and off (I will do that too). And if for some reason it takes longer to establish an IP then you'll have to delay the quickcreds program so it waits until you have an IP.
  9. Don't give up we'll get this. Ok sorry but I'm going to ask some repeated questions just to verify I'm not missing anything. Let me explain assumptions I made on my system to see if it mostly matches yours. From the picture up top that I drew, I have my pc which is a windows 7 box. I have a server 2012 r2 essentials box that I did my best to match yours. I have a win xp box that we'll say is your camera system although it sounds like you have an nvr which I'm not familiar with but we'll get to that. So between the Hak5 video and a plain server 2012 box, when both are connected to the openvpn server in the cloud I can ping the server 2012 box VPN connection from my win7 box. I can ping the openvpn server from my win7 box as well as from my server 2012 box. Separately I can also ping my win xp box from my server 2012 box. I believe you said you could do all that. I can also RDP from my win7 box to my server 2012 box and from my server 2012 box to my win xp box. Again currently with no changes to my server 2012 box I can NOT ping or RDP from my win7 box to my win xp box. And as long as you can do all of that then basically this is where we began. Again sorry to repeat myself but as long as we both have the above then all of that is good and we no longer have to focus on it. Here's one thing I know I didn't ask this particular way... On my setup my "home network" I set to a 172 network. On my "work network" I setup a 10 network. I do not recall what the VPN server IP range was but it was different for both networks and was NOT a 172 or a 10 network. With that said when I first set this up and got it running all I could ping on the server 2012 box was that VPN network IP address. Initially I could not ping the 10 address. Is this true for you too? According to what you had above it looks like a 142 network? So with that said you can ping the 142 correct? Can you ping your work network? Could you ever? Until I enabled routing and NAT I was never able to ping my 10 network even the 10 IP on the server itself. So with routing and NAT can you ping your work network? Then from there do you have a PC that could act like my win xp box just in case there is something blocking your NVR system? I'd like to make sure we can finally get to your work network and maybe another box on that network before going directly to the NVR. Maybe there are some ports we have to open on the server 2012 box to get the NVR to see through it.
  10. Hopefully not too silly of a question but any chance you have another machine to test this on? Maybe something is up with Windows 10 not recognizing the network. For the test I did I simply loaded a fresh install of win10 on an older box, gave it a username and password and plugged in the BB. If that's not an option could you load up vmware or virtualbox and throw together a simple win10 test vm? As long as the BB hits the vm first it'll load and run it's payload just as if it were on a physical box. MS has a few free test VMs you can download as well. If your able to do either of the above I'd be curious on the outcome. Also what version of win10 are you using? There's so many milestones on win10 maybe a certain version is broke. I'll check what I used and let you know as well as upgrade or downgrade to whatever version your using just to check as well.
  11. Here are a few pics: First pic are my networks. The current network that is disconnected in my VPN (Ethernet) and then my physical connection (Ethernet0). The the second pic shows Ethernet0 being the only network added to my NAT. And that's all I had to do. Let me know if you have any luck.
  12. I'll attach a few pics of what mine looks like once I'm back in front of that computer. I'm guessing some of that must have been setup before we added NAT but I don't have IGMP or DCHP. Anyways I followed this video: And like you I added everything at first like your first pic. That didn't work, then following the video I only added my network. Not my VPN just my network. So from your second pic if Local Area Network doesn't work, try Ethernet then Ethernet 2 and see if either of them work. It seemed backwards to me when I did it but once you have it right, it'll just start working. No reboot or refresh is needed. I instantly saw pings and was able to RDP. Again once I'm back in front of my box I'll take a few pics but I had Ethernet and Ethernet 2 only. And Ethernet is what did it for me. Hope this helps.
  13. You know I got to be honest it does seem that you have a networking issue on your bunny. Here's what I have so far: My bunny is at firmware 1.3 I checked my installed-tools file and it shows Installed Tools: ---------------- impacket responder However I followed your first post and noticed that in the root folder the tools folder was empty. I loaded quickcreds into switch 1, plugged it into my fresh win10 box and sure enough I got a slow red blink. I again went to your post, grabbed the deb files and put them in the tools folder, rebooted the bunny, saw that they are now in the root tools folder and ran the install script. I plugged the bunny back into my win10 box and sure enough everything ran just fine. In my loot file is my user and hashed password. I'm curious why my installed tools file showed them installed even though they weren't. Maybe they were at one point? I'm curious did you mess with any networking at all on the bunny? I typed in systemctl status isc-dhcp-server and under Active I have inactive (dead) which is to be expected in arming mode. I can try it with just an RNDIS ethernet running but I'm sure it'll be fine since it loaded up on my win10 box just fine. I'm going to read through the weirdness post that you copied in but I do have one recommendation that might be worth a shot. Can you change your firmware to 1.3? I never upped mine to 1.5 and I've been hearing some talk about the latest firmware on all hak5 gadgets having some issues for some. Just my two sense. I'll keep digging and try to help where I can.
  14. Yeah if you haven't already I'd look into making sure the server is setup for routing with NAT. If you recall from Darren's video, he spent most of it explaining how a reverse VPN works and setting up OpenVPN AS. Then at the very last minute of the video he explained how to setup the turtle to route the traffic between the VPN or "tun" connection on the turtle and the lan or "wan" on the turtle. So basically you'll have to do the same to your server since it's acting as the turtle. The server needs to know how to route or translate the VPN traffic through the existing network.
×
×
  • Create New...