Skip to content
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

Open
iainbrighton opened this issue Jan 4, 2016 · 6 comments
Open

VMSwitch: Add NAT virtual switch support #40

iainbrighton opened this issue Jan 4, 2016 · 6 comments
Labels
enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.

Comments

@iainbrighton
Copy link
Contributor

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.

@rchaganti
Copy link
Contributor

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.
https://github.com/rchaganti/DSCResources/tree/master/cHyper-V/DSCResources/cNatSwitch

Thoughts?

@iainbrighton
Copy link
Contributor Author

@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.

@kwirkykat kwirkykat added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Aug 18, 2016
@iainbrighton
Copy link
Contributor Author

@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?

@PlagueHO
Copy link
Member

@iainbrighton @rchaganti @kwirkykat - Good point. Perhaps xNetworking is a more appropriate location?

@rchaganti
Copy link
Contributor

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.

@PlagueHO
Copy link
Member

@rchaganti - Nice! 😁

@kwirkykat kwirkykat removed the help wanted The issue is up for grabs for anyone in the community. label Oct 25, 2016
@johlju johlju added the help wanted The issue is up for grabs for anyone in the community. label May 16, 2018
@johlju johlju changed the title Add NAT virtual switch support to xVMSwitch VMSwitch: Add NAT virtual switch support Jun 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
Development

No branches or pull requests

5 participants