Repository navigation
Add Server 2016 NAT support聽#44
Description
With Server 2016 TP3+, there is a new NAT virtual switch type. This would be an excellent addition to the module (I wish it was included in Windows 10 too 馃槧). However, in the first instance, it will need some additional metadata in the configuration document..
Activity
[-]Add Serv 2016 NAT support[/-][+]Add Server 2016 NAT support[/+]DexterPOSH commentedon Jan 4, 2016
@iainbrighton I can work on adding this NAT support.
I have a Server 2016 box , where I am already playing with the Module.
iainbrighton commentedon Jan 4, 2016
@DexterPOSH - Thanks for volunteering! 馃槂
Just a word of warning - as we're using the xVMSwitch from the xHyper-V DSC resources to configure the virtual switches, this functionality will first need to be put into the official https://github.com/PowerShell/xHyper-V resource. I have opened an issue dsccommunity/HyperVDsc#40 to implement this functionality.
Are you still happy to implement this functionality over there first? Once complete, we can then enable NAT functionality here?
DexterPOSH commentedon Jan 4, 2016
@iainbrighton Thanks for the heads up.
Let me try and see if I can finish this early, if am able to do that I will do a PR to the parent repo.
iainbrighton commentedon Jan 6, 2016
@DexterPOSH @csandfeld - FYI - It looks like NAT support is included on Win 10 build 10586. I might be seeing the NAT -SwitchType be because I have the RSAT tools installed?! Regardless, I have a NAT virtual switch up and running on build 10586 馃槂
From other Twitter conversations, it looks like the New-VMSwitch implementation might be changing, at least that it what it looks like in the later Win 10 build 11082. If this is the case, we're all going to be in for a bumpy ride 馃槵
csandfeld commentedon Jan 6, 2016
NAT support on Win 10 馃憤
Changing New-VMSwitch implementation 馃憥
kilasuit commentedon Jan 6, 2016
Win 10 11082 allows me to specify NAT as the Switch type although it seems that the Help Needs updating to reflect that this has been included - not updated either after running Update-Help -Force
I reckon its part of either the implemented version of HyperV or possibly via RSAT tools
But you can create a NAT Switch with the below
Poor example but yeah its in there
iainbrighton commentedon Jan 6, 2016
kilasuit commentedon Jan 7, 2016
Didnt have it installed when I ran it - though I do now and it installed fine using my Install-Win10RSATTools function https://github.com/kilasuit/PoshFunctions/blob/Dev/Scripts/Install-Win10RSATTools.ps1
DexterPOSH commentedon Jan 7, 2016
@iainbrighton I spoke to Ravikanth at work and he already has a NAT VM switch implementation in his repo. He will be doing a PR soon to the xHyperV repo.
I will be going through that and see how we can fit those changes here.
iainbrighton commentedon Jan 8, 2016
@DexterPOSH Excellent! This is what I have run on my Win10 machine:
I think we're going to need a NAT translation DSC resource. What repo this goes into, I haven't a clue at the moment! It may need a new 'xNAT' repo or put into the xNetworking repo?
DexterPOSH commentedon Jan 8, 2016
@iainbrighton I see the code pushed upstream by Ravi.
https://github.com/rchaganti/DSCResources/tree/master/cHyper-V/DSCResources/cNatSwitch
iainbrighton commentedon Jan 11, 2016
@DexterPOSH I don't see any reference to a
New-NetNatequivalent resource? I'm sure this will need working as well?DexterPOSH commentedon Jan 12, 2016
@iainbrighton, I do see New-NetNat being used in the Set-TargetResource definition in the psm1 file.
iainbrighton commentedon Jan 12, 2016
@DexterPOSH I'm not 100% convinced that that's the right place for it. What happens when I need an alternative NAT configuration?
IMHO the resource shouldn't be making any assumptions, but that's probably a conversation that needs to happen over at dsccommunity/HyperVDsc#40