16
16.7 Legacy Series / OPNSense (Hyper-V) w/Private Internet Access VPN
« on: December 30, 2016, 04:05:49 am »
I currently am running a new OPNsense setup...
I have a Windows Server 2016 on a computer running Hyper-V with OPNsense installed.
Utilizing 2 NIC's... one for WAN (Cable Modem Attached), and one for LAN to my switches in my house with other wired devices utilizing Hyper-V Virtual Switches.
This is working great after I got it all setup today...
The next question is that I have a subscription to PIA (Private Internet Access) VPN.
I would like to route (most) of my traffic through this... with exception to a few devices such as my home security system, Wi-Fi calling cell phones, and a few other things.
I was wondering what would be the easiest way to segment some of the network traffic and use PIA in an OpenVPN Client setup?
Would VLANs be best and route an entire VLAN through the VPN? or create another virtual interface and static route through the VPN?
I am open to suggestions or if anyone can point me to a guide that has done this sort of setup before...
Thanks!
I have a Windows Server 2016 on a computer running Hyper-V with OPNsense installed.
Utilizing 2 NIC's... one for WAN (Cable Modem Attached), and one for LAN to my switches in my house with other wired devices utilizing Hyper-V Virtual Switches.
This is working great after I got it all setup today...
The next question is that I have a subscription to PIA (Private Internet Access) VPN.
I would like to route (most) of my traffic through this... with exception to a few devices such as my home security system, Wi-Fi calling cell phones, and a few other things.
I was wondering what would be the easiest way to segment some of the network traffic and use PIA in an OpenVPN Client setup?
Would VLANs be best and route an entire VLAN through the VPN? or create another virtual interface and static route through the VPN?
I am open to suggestions or if anyone can point me to a guide that has done this sort of setup before...
Thanks!