Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • NAT is a kludge that is simply intended to extend the life of IPv4 until IPv6 is ubiquitous. It is not intended to replace routing. If you have non-overlapping private networks, simply route between the networks, not use NAT.
    – Ron Maupin
    Commented Oct 6, 2019 at 22:00
  • I agree. But you need win 10 server (not pro) to configure decent routing, afaik. The routes would need to be modified whenever the software VPN kicks in and out too. This NAT thing is set and forget.
    – init_js
    Commented Oct 6, 2019 at 22:03
  • 1
    I have done the same thing (including step 4) and I can ping my vSwitch gateway as well as the actual router gateway and any other IP, however DNS just does not work... nslookup, dig, ping all fail miserably :-( I tried on Fedora and Ubuntu - I am pretty sure this is an issue with the vmswitch Commented May 16, 2020 at 19:47