Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
NAT routing conflicts with Hyper-V vms NAT
See original GitHub issueWindows NetNat currently supports a single NAT instance, this means that using WgServer takes it over preventing HyperV VMs from using the NAT feature.
Ms proposed solution is to configure a single NAT shared by multiple adapters.
I’m fine with WgServer managing the NetNat configuration, however i’d like to ask for an “advanced configuration” option where the user can set a custom value for the InternalIPInterfaceAddressPrefix option (with sanity checks to make sure it includes wireguard’s IP range), this way the NAT can be shared by multiple network adapters.
Issue Analytics
- State:
- Created 5 months ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s working perfectly, thanks for the quick release.
I mean yeah I could try but I’d like my VPN to be reliable and not have to do debugging the next time i need it 😅
For the time being I’m just not using hyperv but I’d like for this be implemented as apparently it’s how Ms says it’s meant to be done (arguably, an hacky solution on their end)