From the course: Protecting Your Network with Open-Source Software

Environment setup

- [Instructor] Deploying virtual machines, or VMs, in a virtualization environment is relatively straightforward and out of scope for this course. However, there are some subtle things you need to keep in mind to avoid potential dead ends. I had to create two virtual subnets with the following subnet IDs. 192.168.70.0/24 and 192.168.35.0/24. The 192.168/24 network does not have direct access to the internet while 192.168.70/24 does. The 192.68.35.0/24 network eventually gets connected to the internet through the Ubuntu router host. Make sure that you change the network gateway of your Ubuntu host to 192.168.35.136, which is the internal network interface of the Ubuntu router host, so that the Ubuntu host knows how to get to the 192.168.70.0/24 network and the internet. Whenever you restart your Ubuntu router VM, the forwarding option is disabled by default. Therefore, you need to enable forwarding each time by issuing the command echo 1 > /proc/sys/net/ipv4/ip_forward If you don't want to use VMware workstation to try out the hands-on exercises, you can check out cloud solutions like Microsoft Azure or try a hypervisor like Proxmox, which is a dedicated operating system specializing in installing VMs on a local machine.

Contents