Jump to content

Bob123

Active Members
  • Posts

    202
  • Joined

  • Last visited

  • Days Won

    7

Recent Profile Visitors

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

Bob123's Achievements

  1. Could you start a new thread and describe what your trying to do when you mean run multiple scripts?
  2. But that's the thing that I think your getting confused on. There are no USB static IPs on computers that are just sitting around. When you plug in the lan turtle via USB you are creating that "virtual" network. There was nothing there before it. So by default it'll be dynamic (DHCP). I can't think of a reason of why you'd want to make it static but I guess the option is there. But it is not a TRUE ethernet network. Think of it as a virtual network between you and the lan turtle or that pc and the lan turtle. So hopefully that wasn't too confusing but to answer your question above. If the computer has a static IP of 10.10.50.102 that is a physical ethernet connection. The lan turtles 172.16.84.x network is a virtual network between the lan turtle and that computer. So that computer will automatically get am IP of 172.16.84.x. It'll still have the 10 network because that's a different network. So at that point it'll have two networks. Hope this helps.
  3. Just going by your message and nothing else. Are you referring to the network connection over eithernet or the network connection over USB? Cause those are two different things. When you plug in the lan turtle over USB to your computer it makes it's own "network" connection and get a DHCP IP from the lan turtle. Once you know what it's IP is then you could give your PC a static IP if you prefer. If you are referring to the lan turtle's network port, it's been a while but I believe you give the turtle itself an IP to make the network your going to plug it into. At least that's how I've done it in the past.
  4. 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.
  5. 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.
  6. What was the boot setting you had to change?
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Ok to just to verify a few things, from Server 2012 you can get to the camera machine correct? And with your machine at home or whatever, you can connect to openvpn, Server 2012 can also connect to openvpn, and you can see Server 2012 from your machine correct? Can you RDP to the server? Depending on the admin rights you have to that server you could always just RDP from there to the camera machine. If that won't work for you then you'll have to setup routing and NAT on the Server 2012 box. Do you have any of that setup? If not what you'll have to do is add a role. I selected both routing and the remote access and vpn roles. Once those are installed open the getting started wizard on the direct access and vpn, and choose the bottom which is deploy vpn only. Once that opens you'll see two server looking devices, right click on the second one (local) and click on configure. Then you'll select custom and lan routing. Once that's done you'll see you now have IPv4 and IPv6, under IPv4 you'll see general, right click on general and add a new routing protocol. We'll add NAT. Then from NAT we'll want to add our network. Make sure you only add your actual network and not your VPN network. And really that's all there is to it. Once I added that I was able to browse my "work network." So from my pic above I had a machine on it's own network, a work network with Server 2012 and an XP box. I connected my machine and Server 2012 to an OpenVPN AS in the cloud. Once I enabled routing and NAT on Server 2012 I was able to then see the entire work network, including the XP box and was able to remote into it. Hopefully adding routing and NAT is all you're missing. Let me know if any of this works or if you need any other help.
  13. I'm helping someone else with a situation not much unlike yours. Are you just trying to connect to your RPI remotely? The video you are referring to has a VPS in the cloud. Are you using that? Are both the RPI and your laptop accessing that OpenVPN server in the cloud? If not then you'll have to do some routing on the RPI side to get it to work. Check out this diagram. The top is what Darren and Shannon did on Hak5, the bottom is more of your traditional VPN where you have to open ports and do routing. Just replace the Server 2012 with your RPI in the diagram.
  14. So does your setup look like the the top setup with a virtual private server or the second setup where OpenVPN is installed on Server 2012 at your work or other location? Just trying to get an idea of the setup. I'm setting up my Server 2012 now and just trying to visualize where to place it. Of the above two drawings, the top one is more of what Hak5 was trying to visualize but with a lan turtle or packet squirrel between the VPS and the Server 2012. The second drawing is more of your typical work VPN where the Server 2012 box is also a NAT/firewall and it's forwarding network traffic from one network to another. Note that if you have OpenVPN installed on the Server 2012 box which is on the same site as the camera PC, the camera PC needs to have a client.ovpn file on it as well, or you'll have to do some firewall work and you'll have more of a standard VPN setup to where once you are logged in, your basically just on your work network. Let me know if this makes any sense. If it doesn't I can try to explain it again. I've gotten this to work many times using the lan turtle and packet squirrel. It's about time I do it with several PCs.
×
×
  • Create New...