-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMSwitch: Add NAT virtual switch support #40
Comments
Do you think this should be a separate resource? If you are creating a NAT switch there are certain other steps that we need to perform such as setting the IP Range and Subnet. I have a resource that is already written for this and I can push it here. Thoughts? |
@rchaganti I would love to see that functionality merged in! The only reason I mention a separate resource is if the NetNat cmdlets be used with some other functionality than the virtual NAT switch, like RRAS? If so, I think they probably should be in a separate resource. |
@rchaganti @PlagueHO @kwirkykat Now that Server 2016 is officially out, can we think about implementing this? The *-NetNat cmdlets aren't really Hyper-V specific, so should they be in the xHyper-V module or another/different module? |
@iainbrighton @rchaganti @kwirkykat - Good point. Perhaps xNetworking is a more appropriate location? |
xNetworking is suitable for this given that this has nothing to with VM switches. I am in the process of refactoring cHyper-V and push this to xNetworking. |
@rchaganti - Nice! 😁 |
With the introduction of Server 2016 TP3/TP4 there is a new NAT virtual switch type. This should be added to the xVMSwitch resource. How the NAT specific properties are handled will need to ironed out before implementing.
The text was updated successfully, but these errors were encountered: