#SOPHOS XG FIREWALL HOME EDITION. ... FULL#

The WAN port is set to grab an address from DHCP so you’ll need to determine which IP address this is either by going into your physical router, or using a tool like Angry IP. To do so, choose option 4 to enter the device console and enter the following command: system appliance_access enable So what do we do? We need to run a command to enable admin access on the WAN port. Unfortunately, this will not work since the LAN side has no physical uplinks. Once this is done, you would normally navigate to that address on port 4444 to access the admin GUI.

Login to the console with the default ( admin – admin) credentials, and choose the option for Network Configuration to change the IP for your nested LAN port. This will need to be changed to the subnet you’re using for your nested LAN interface. Once the VM has been deployed, the Sophos XG will be configured with a 172.16.1.1 address by default.

Boot: BIOS (will not boot if you keep as EFI).

Network Adapter 1: LAN portgroup (nested).

Disk: 40GB thin (you may make this smaller if you’d like).

RAM: 2GB (add more as needed – max supported is 6GB in the home edition).

CPU: 1 (add more as needed – max supported is 4 in the home edition).

#SOPHOS XG FIREWALL HOME EDITION. ... FULL#

I’ll describe the basics for deploying the Sophos XG firewall, but will not go into full detail as this is pretty trivial and can be deployed using the following guide as a reference.

With that said, one of the VLANs I have is for “Development” work, such as this so I’ll be connecting one uplink from the router to this VLAN which will serve as the WAN interface while the other uplink will be connected to the new nested portgroup to serve as the LAN for the nested lab. I have a bunch of VLANs created for my physical Home Lab as I’ve yet to deploy NSX-T in there, but once I do, I’ll be removing the majority of said VLANs and only keeping the required ones needed to run the lab. Once you determine the subnets you’d like to use for the nested lab, add a static route summary on your physical router.Static route to access the nested lab from my LAN.Set the VLAN type for this portgroup to VLAN Trunking with the range of 0-4094 to allow all VLANs to trunk through.VDS and portgroup without physical uplinks.All traffic will flow through virtual router/firewall to communicate to and from the nested lab.

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. In this post, I will cover the setup and configuration of a Sophos XG firewall Home Edition which will serve as the router for my nested lab environment. In my previous post, I went over the gist of what I plan to do for my nested NSX-T Home Lab. Welcome to Part 1 of my NSX-T Home Lab Series.

Sophos xg firewall home edition. ...