Possibly my final post for 2015, but maybe not. It really depends on my sleep patterns, mood, and free time. And then there’s the holiday alcohol factor too, so who knows. This isn’t going to be an in-depth discussion of the forthcoming NAT virtual switch in Windows 10 Hyper-V. For that I would recommend you read the 4Sysops article.
Here’s my kool aid spin on the PowerShell code (fwiw):
$prefix = "192.168.1.0/24" $swName = "NAT" New-VMSwitch -Name $swName -SwitchType NAT -NATSubnetAddress $prefix New-NetNat -Name $swName -InternalIPInterfaceAddressPrefix $prefix
NAT Switch Pro’s/Con’s
My thoughts on this new feature, as it stands in the current state, for whatever value my opinion provides, are as follows:
- It’s indeed welcome. Long overdue, but nice to have.
- It’s nowhere near as capable or useful as the alternatives offered in VMware products.
- If you need to build out a lab environment with multiple LAN segments, and you want to make it more realistic than using a Windows VM with RRAS, create a dedicated “router” VM using DD-WRT.
- It is literally a NAT switch. Not a firewall.
- The current feature-set in 11082 leaves you having to make a few tweaks after running the PowerShell cmdlets, mainly for the external side
These are already posted by others in the Windows 10 feedback forum:
- Add the NAT switch type into the GUI forms (virtual switch manager)
- Allow more settings to be modified while a VM is running, such as adding hardware.
- Make better use of the VM details reporting in the bottom panel.