-
Notifications
You must be signed in to change notification settings - Fork 79
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
NAT Routing Error #30
Comments
Hey @crack00r, can you send the exact version of Windows you're running? From the Start menu or Run box, type Thanks! |
@crack00r I would still like to hear what version of Windows you're running, but I think I know what's going on here. The NAT routing features requires either...
Of course Internet Connection Sharing can always be used if NAT cannot. I've documented this limitation here. I will keep the issue open to track an enhancement, which should do the following.
|
Thanks for confirming! This aligns with my guess.
I'm glad to hear that ICS works. And if you did want to use NAT instead (it has some benefits described in #18), you could update to 21H2. As mentioned, I will keep this issue open, because the NAT button should not have been available in your scenario. |
Upon further investigation (with Windows 10 Pro 21H2), it appears that Hyper-V must be enabled in order to use NAT Routing. @kenvix, you said in #18 that it didn't. Can you explain how you got For now, I've updated the documentation to reflect this. |
I am not kenvix, but I installed WireGuard Server for Windows on Windows 10 pro 21H2 Build 19044.1620 yesterday without problems. And no, Hyper-V is not enabled. At least I believe it isn't: In Windows Features "Hyper-V" is unticked. After some testing on the Win Pro machine, I have installed WireGuard Server for Windows on Windows Server 2019 which has an old Windows 10 under the hood: Version 1809, Build 17763.2686. Everything works surprisingly well. |
Hmm, interesting. Now I wonder if my problem could've been related to the fact that I was using VMs to test this without nested virtualization enabled. I will have to do some more investigation. |
Now I'm going to confuse you even more... I just tried WireGuardServerForWindows on Windows 10 Pro N Version 21H2 Build 19044.1620 and enabling NAT failed! |
I'm getting the impression that I won't be able to add a simple version check to gate this feature. 😊 It seems like I will need some sort of graceful handling of this error that does the following...
|
Hey all, I just pushed v1.7.2 which should help to address this issue. As we collectively discovered, there's not a great way to know upfront whether NAT Routing will work or not, so the application just tries to enable it (with the option to try to enable Hyper-V as well); otherwise, it directs you to use ICS. |
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.Exception: New-NetNat : Ung�ltige Klasse
In Zeile:1 Zeichen:1
System.Exception: New-NetNat : Ung�ltige Klasse
In Zeile:1 Zeichen:1
The text was updated successfully, but these errors were encountered: