I've set up a small Hyper-V Active Directory test lab which is isolated from our production network. I have set it up using a separate internet line that we use for guest WiFi access.
I have the Hyper-V server on a static IP address on a 192.168.1.xx address.
I have then created a VM running PfSense router to provide the VMs internet access and to further segregate them. The VMs are connected to a separate Private switch that use IP addresses on 10.10.1.xx range.
I have got the basic connectivity working now, but I am just wondering if it is possible to use the PfSense to act as a VPN so I can connect into the AD domain from home etc.
I'm not looking for detailed instructions on setting it up, but just to know if its possible, or whether I need to approach it in a different way.
Thanks for the link, definitely a good read. What I can't quite get my head round is how I get access to the VMs that are on the 10.10.1.xx range as the Hypervisor, and any other clients I guess are on the 192.168.1.xx range, much like how it is set up in a residential setting. So I can see how I could connect via the VPN to those machines e.g. the hyper-v server, but not the actual VMs.
Or does the router part of pfsense handle all of this ?
Just like to properly have my head round stuff before I get stuck in
I'm sure I'm missing something pretty obvious but just can't seem to join up all the dots.
If anyone has anymore tutorials or guides that would be great.