{"id":1794,"date":"2023-04-23T17:03:00","date_gmt":"2023-04-23T21:03:00","guid":{"rendered":"https:\/\/ithinkvirtual.com\/?p=1794"},"modified":"2023-04-26T18:57:39","modified_gmt":"2023-04-26T22:57:39","slug":"nested-vsphere-home-lab-part-1-sophos-firewall","status":"publish","type":"post","link":"https:\/\/ithinkvirtual.com\/2023\/04\/23\/nested-vsphere-home-lab-part-1-sophos-firewall\/","title":{"rendered":"Nested vSphere Home Lab \u2013 Part 1 \u2013 Sophos Firewall"},"content":{"rendered":"\n

intro<\/h2>\n\n\n\n

Welcome to Part 1 of my Nested vSphere Home Lab Series.  In my previous post<\/a>, I went over the gist of what I plan to do for my nested Nested vSphere<\/a> Home Lab.  In this post, I will cover the setup and configuration of a Sophos XG Firewall Home Edition<\/a> which will serve as the router for my nested lab environment.  My physical Home Lab is configured with Virtual Distributed Switches, or VDS (sometimes seen as DVS) for short, and since this is a nested lab environment that will not have any physical uplinks connected, I will need to create a new VDS without physical uplinks connected to it along with a portgroup for the nested environment and then configure access to the environment from my LAN.  This can also be configured on a Virtual Standard Switch, or VSS for short, in the same fashion.  All network traffic will flow through the virtual router\/firewall to communicate to and from the nested lab.  Afterward, I’ll cover the Active Directory Server setup.<\/p>\n\n\n\n

Router<\/h3>\n\n\n\n

Prerequisites:<\/strong><\/p>\n\n\n\n