![Dropbox api key](https://cdn1.cdnme.se/5447227/9-3/screenshot_5_64e62947ddf2b306ca76f796.jpg)
The packet will go to the router, 10.10.10.2, but that packet will drop it as non-routable. When it tries to send a packet back, the destination IP will be 192.168.223.120, and it doesn’t know how to get it there. But when the packet reaches a HTB machine, the source address will be 192.168.223.120. It is enough to get packets from Windows to HTB. This says that for any destination on 10.10.10.0.23, the packet should route to 192.168.223.110, the Parrot VM. If that is set to 1, the OS will allow routing of packets. Linux has a setting that’s stored in /proc/sys/net/ipv4/ip_forward. If you’re just setting this up, assign the IPs to the VM network and then make sure you can ping each box from the other. With the VPN connected, the network looks like: Then I gave each box a static IP on that interface.
![parrot virtualbox network settings parrot virtualbox network settings](https://1.bp.blogspot.com/-hj8EtkJUTZs/W44QorQm7VI/AAAAAAAAKqI/aBmr9ORhmWEetkOiApzL4EC-1O4Hgem9gCEwYBhgL/s1600/3.png)
I’ve configured my VMs such that each has a second NIC that they can use to talk to each other. This post shows how I configured my VMs so that Windows traffic can route through the Linux VM to HTB.
![parrot virtualbox network settings parrot virtualbox network settings](https://media.geeksforgeeks.org/wp-content/uploads/20210630121224/5-660x469.png)
![parrot virtualbox network settings parrot virtualbox network settings](https://i.ytimg.com/vi/ouFianXU_C0/maxresdefault.jpg)
Some of those times, I’ll need to interact with the HTB machines over the VPN from the Windows host, and it’s always a bit of a pain to turn off the VPN in the Linux VM, and then turn it on from Windows. When doing HTB or other CTFs, I typically run from a Linux VM (formerly Kali, lately Parrot), but I also need to use a Windows VM from time to time as well.
![Dropbox api key](https://cdn1.cdnme.se/5447227/9-3/screenshot_5_64e62947ddf2b306ca76f796.jpg)