Windows 10 pro as a NAT between two interfaces (to route VM traffic trough a VPN connection on the host) ...
Is a distribution that is normal, but highly skewed considered Gaussian?
What connection does MS Office have to Netscape Navigator?
Why do airplanes bank sharply to the right after air-to-air refueling?
Chain wire methods together in Lightning Web Components
Why isn't acceleration always zero whenever velocity is zero, such as the moment a ball bounces off a wall?
Powershell. How to parse gci Name?
Method for adding error messages to a dictionary given a key
Break Away Valves for Launch
Is French Guiana a (hard) EU border?
Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?
Bartok - Syncopation (1): Meaning of notes in between Grand Staff
Is there a way to save my career from absolute disaster?
Reference request: Grassmannian and Plucker coordinates in type B, C, D
How many extra stops do monopods offer for tele photographs?
Recycling old answers
How did people program for Consoles with multiple CPUs?
0 rank tensor vs 1D vector
If Nick Fury and Coulson already knew about aliens (Kree and Skrull) why did they wait until Thor's appearance to start making weapons?
Is there a difference between "Fahrstuhl" and "Aufzug"
Why don't programming languages automatically manage the synchronous/asynchronous problem?
Proper way to express "He disappeared them"
Do I need to write [sic] when a number is less than 10 but isn't written out?
Is wanting to ask what to write an indication that you need to change your story?
Why is Germany producing more waste than US?
Windows 10 pro as a NAT between two interfaces (to route VM traffic trough a VPN connection on the host)
The Next CEO of Stack OverflowRRAS VPN Server on Windows 2008 Behind NATHow to route different traffic thru different network interfaces (in Windows)How to keep general internet traffic off Windows 2008 R2 VPN and only handle VPN traffic?Route VPN Traffic From Linux Box To Windows BoxHow to route traffic over an active VPN tunnel by domain name?Is it possible to bridge/join two or more vritual (Hyper-V) switches with the same address range over VPN?openvpn route ALL traffic through VPN but through particular client (not server)NAT with two upstream interfaces?OpenVPN on Windows 10 without redirect-gateway option, or with options just to handle VPN trafficHow to route traffic from host in VPC via host in different VPC
I have a windows 10 pro host with VMs running in Hyper-V. The VMs are on a private LAN with the host. I would like to provide internet connectivity to the VMs, and have the VM traffic go through the VPN connection configured on the host. The particular software VPN (pulse secure) doesn't create an interface that is "bridgeable" with the vswitch.
My hyper-V VMs are on 192.168.4.0/24, and my windows 10 host has a virtual interface on 192.168.4.215/24 which I would like to use as a gateway for the VMs traffic. I would like to use the routing tables on the windows host to route traffic from the VMs on 192.168.4.0/24 to go through a VPN interface configured on the host.
I normally provide internet connectivity to VMs by putting them on a LAN, creating a virtual interface for the host on that same LAN, and then bridging the virtual interface to a physical interface (either a physical NIC or a wireless NIC). In this case however, VM traffic would bypass the software VPN configured on the windows host -- I would like the VM traffic to be routed through the VPN, the same way that traffic from host applications are routed.
When I activate the VPN connection (pulse secure), a new virtual interface shows up on the host, at 10.0.0.100/32, and a default route is automatically added to the host's routing table to point to 10.0.0.100 as the default gateway. This effectively makes all of the external traffic generated by the windows host and its desktop applications go through the vpn interface.
I would like to configure the host to re-route/forward all incoming IP traffic from 192.168.4.0/24 onto the VPN interface, possibly NATed. Normally I would bridge the interfaces I want to connect together, but this particular vpn adapter will refuse to be bridged to anything.
Is there a way to achieve this in win10 pro, or do I need windows server? This is annoying also because this particular vpn software isn't well supported in Linux.
networking vpn nat windows-10
asked May 10 '18 at 7:37
init_jsinit_js
10627
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a windows 10 pro host with VMs running in Hyper-V. The VMs are on a private LAN with the host. I would like to provide internet connectivity to the VMs, and have the VM traffic go through the VPN connection configured on the host. The particular software VPN (pulse secure) doesn't create an interface that is "bridgeable" with the vswitch.
My hyper-V VMs are on 192.168.4.0/24, and my windows 10 host has a virtual interface on 192.168.4.215/24 which I would like to use as a gateway for the VMs traffic. I would like to use the routing tables on the windows host to route traffic from the VMs on 192.168.4.0/24 to go through a VPN interface configured on the host.
I normally provide internet connectivity to VMs by putting them on a LAN, creating a virtual interface for the host on that same LAN, and then bridging the virtual interface to a physical interface (either a physical NIC or a wireless NIC). In this case however, VM traffic would bypass the software VPN configured on the windows host -- I would like the VM traffic to be routed through the VPN, the same way that traffic from host applications are routed.
When I activate the VPN connection (pulse secure), a new virtual interface shows up on the host, at 10.0.0.100/32, and a default route is automatically added to the host's routing table to point to 10.0.0.100 as the default gateway. This effectively makes all of the external traffic generated by the windows host and its desktop applications go through the vpn interface.
I would like to configure the host to re-route/forward all incoming IP traffic from 192.168.4.0/24 onto the VPN interface, possibly NATed. Normally I would bridge the interfaces I want to connect together, but this particular vpn adapter will refuse to be bridged to anything.
Is there a way to achieve this in win10 pro, or do I need windows server? This is annoying also because this particular vpn software isn't well supported in Linux.
networking vpn nat windows-10
asked May 10 '18 at 7:37
init_jsinit_js
10627
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51
add a comment |
I have a windows 10 pro host with VMs running in Hyper-V. The VMs are on a private LAN with the host. I would like to provide internet connectivity to the VMs, and have the VM traffic go through the VPN connection configured on the host. The particular software VPN (pulse secure) doesn't create an interface that is "bridgeable" with the vswitch.
My hyper-V VMs are on 192.168.4.0/24, and my windows 10 host has a virtual interface on 192.168.4.215/24 which I would like to use as a gateway for the VMs traffic. I would like to use the routing tables on the windows host to route traffic from the VMs on 192.168.4.0/24 to go through a VPN interface configured on the host.
I normally provide internet connectivity to VMs by putting them on a LAN, creating a virtual interface for the host on that same LAN, and then bridging the virtual interface to a physical interface (either a physical NIC or a wireless NIC). In this case however, VM traffic would bypass the software VPN configured on the windows host -- I would like the VM traffic to be routed through the VPN, the same way that traffic from host applications are routed.
When I activate the VPN connection (pulse secure), a new virtual interface shows up on the host, at 10.0.0.100/32, and a default route is automatically added to the host's routing table to point to 10.0.0.100 as the default gateway. This effectively makes all of the external traffic generated by the windows host and its desktop applications go through the vpn interface.
I would like to configure the host to re-route/forward all incoming IP traffic from 192.168.4.0/24 onto the VPN interface, possibly NATed. Normally I would bridge the interfaces I want to connect together, but this particular vpn adapter will refuse to be bridged to anything.
Is there a way to achieve this in win10 pro, or do I need windows server? This is annoying also because this particular vpn software isn't well supported in Linux.
networking vpn nat windows-10
asked May 10 '18 at 7:37
init_jsinit_js
10627
I have a windows 10 pro host with VMs running in Hyper-V. The VMs are on a private LAN with the host. I would like to provide internet connectivity to the VMs, and have the VM traffic go through the VPN connection configured on the host. The particular software VPN (pulse secure) doesn't create an interface that is "bridgeable" with the vswitch.
My hyper-V VMs are on 192.168.4.0/24, and my windows 10 host has a virtual interface on 192.168.4.215/24 which I would like to use as a gateway for the VMs traffic. I would like to use the routing tables on the windows host to route traffic from the VMs on 192.168.4.0/24 to go through a VPN interface configured on the host.
I normally provide internet connectivity to VMs by putting them on a LAN, creating a virtual interface for the host on that same LAN, and then bridging the virtual interface to a physical interface (either a physical NIC or a wireless NIC). In this case however, VM traffic would bypass the software VPN configured on the windows host -- I would like the VM traffic to be routed through the VPN, the same way that traffic from host applications are routed.
When I activate the VPN connection (pulse secure), a new virtual interface shows up on the host, at 10.0.0.100/32, and a default route is automatically added to the host's routing table to point to 10.0.0.100 as the default gateway. This effectively makes all of the external traffic generated by the windows host and its desktop applications go through the vpn interface.
I would like to configure the host to re-route/forward all incoming IP traffic from 192.168.4.0/24 onto the VPN interface, possibly NATed. Normally I would bridge the interfaces I want to connect together, but this particular vpn adapter will refuse to be bridged to anything.
Is there a way to achieve this in win10 pro, or do I need windows server? This is annoying also because this particular vpn software isn't well supported in Linux.
networking vpn nat windows-10
networking vpn nat windows-10
asked May 10 '18 at 7:37
init_jsinit_js
10627
asked May 10 '18 at 7:37
init_jsinit_js
10627
edited Feb 27 at 0:27
init_js
asked May 10 '18 at 7:37
init_jsinit_js
10627
asked May 10 '18 at 7:37
init_jsinit_js
10627
asked May 10 '18 at 7:37
init_jsinit_js
10627
10627
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51
add a comment |
1
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51
1
1
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51
add a comment |
1 Answer
1
active
oldest
votes
I've managed to get something working on Windows 10, by creating a HyperV NAT interface. I believe you'll need windows 10 pro for that. Win10 home doesn't have Hyper-V (yet).
This has worked quite well:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network
- Create a NAT interface using powershell using the instructions in the link above. There is apparently a limit of 1 such interface according to the documentation, but on my computer there are currently 2 active vNAT interfaces: one I've created myself, and one called DockerNAT, which got created by Docker for Windows. This step will give you a new vSwitch, and assign it an IP on the host.
- In Hyper-V, edit the VM's settings to add a new network interface connected to the NAT switch interface created in step 1.
- On the VM, assign the new nic a static IP on that NAT subnet (e.g.
ip addr add dev ethX 192.168.0.100/24), and configure the default gateway to be the vSwitch IP, e.g. (route add default gw 192.168.0.1 ethX) - Add any nameserver to /etc/resolv.conf (
e.g. echo "nameserver 8.8.8.8" >> /etc/network/interfaces)
The effect of using the NAT interface is that the traffic coming out of any VM using the NAT vSwitch will be masqueraded behind the gateway IP (192.168.0.1 in my example), and will be re-routed internally using the routing table of the windows host. So, when I turn on the VPN, this will re-route all the Natted traffic to the VPN too.
There are many cases where I want to access the VM from the host directly, which the NAT makes difficult (everything will be behind 192.168.0.1). Rather than doing a bunch of dynamic port forwarding (which is also possible too with powershell), I've simply created another internal network between the host and the VM that is not NAtted (e.g. 192.168.5.0/24.
answered May 10 '18 at 8:35
init_jsinit_js
10627
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f911578%2fwindows-10-pro-as-a-nat-between-two-interfaces-to-route-vm-traffic-trough-a-vpn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've managed to get something working on Windows 10, by creating a HyperV NAT interface. I believe you'll need windows 10 pro for that. Win10 home doesn't have Hyper-V (yet).
This has worked quite well:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network
- Create a NAT interface using powershell using the instructions in the link above. There is apparently a limit of 1 such interface according to the documentation, but on my computer there are currently 2 active vNAT interfaces: one I've created myself, and one called DockerNAT, which got created by Docker for Windows. This step will give you a new vSwitch, and assign it an IP on the host.
- In Hyper-V, edit the VM's settings to add a new network interface connected to the NAT switch interface created in step 1.
- On the VM, assign the new nic a static IP on that NAT subnet (e.g.
ip addr add dev ethX 192.168.0.100/24), and configure the default gateway to be the vSwitch IP, e.g. (route add default gw 192.168.0.1 ethX) - Add any nameserver to /etc/resolv.conf (
e.g. echo "nameserver 8.8.8.8" >> /etc/network/interfaces)
The effect of using the NAT interface is that the traffic coming out of any VM using the NAT vSwitch will be masqueraded behind the gateway IP (192.168.0.1 in my example), and will be re-routed internally using the routing table of the windows host. So, when I turn on the VPN, this will re-route all the Natted traffic to the VPN too.
There are many cases where I want to access the VM from the host directly, which the NAT makes difficult (everything will be behind 192.168.0.1). Rather than doing a bunch of dynamic port forwarding (which is also possible too with powershell), I've simply created another internal network between the host and the VM that is not NAtted (e.g. 192.168.5.0/24.
answered May 10 '18 at 8:35
init_jsinit_js
10627
add a comment |
I've managed to get something working on Windows 10, by creating a HyperV NAT interface. I believe you'll need windows 10 pro for that. Win10 home doesn't have Hyper-V (yet).
This has worked quite well:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network
- Create a NAT interface using powershell using the instructions in the link above. There is apparently a limit of 1 such interface according to the documentation, but on my computer there are currently 2 active vNAT interfaces: one I've created myself, and one called DockerNAT, which got created by Docker for Windows. This step will give you a new vSwitch, and assign it an IP on the host.
- In Hyper-V, edit the VM's settings to add a new network interface connected to the NAT switch interface created in step 1.
- On the VM, assign the new nic a static IP on that NAT subnet (e.g.
ip addr add dev ethX 192.168.0.100/24), and configure the default gateway to be the vSwitch IP, e.g. (route add default gw 192.168.0.1 ethX) - Add any nameserver to /etc/resolv.conf (
e.g. echo "nameserver 8.8.8.8" >> /etc/network/interfaces)
The effect of using the NAT interface is that the traffic coming out of any VM using the NAT vSwitch will be masqueraded behind the gateway IP (192.168.0.1 in my example), and will be re-routed internally using the routing table of the windows host. So, when I turn on the VPN, this will re-route all the Natted traffic to the VPN too.
There are many cases where I want to access the VM from the host directly, which the NAT makes difficult (everything will be behind 192.168.0.1). Rather than doing a bunch of dynamic port forwarding (which is also possible too with powershell), I've simply created another internal network between the host and the VM that is not NAtted (e.g. 192.168.5.0/24.
answered May 10 '18 at 8:35
init_jsinit_js
10627
add a comment |
I've managed to get something working on Windows 10, by creating a HyperV NAT interface. I believe you'll need windows 10 pro for that. Win10 home doesn't have Hyper-V (yet).
This has worked quite well:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network
- Create a NAT interface using powershell using the instructions in the link above. There is apparently a limit of 1 such interface according to the documentation, but on my computer there are currently 2 active vNAT interfaces: one I've created myself, and one called DockerNAT, which got created by Docker for Windows. This step will give you a new vSwitch, and assign it an IP on the host.
- In Hyper-V, edit the VM's settings to add a new network interface connected to the NAT switch interface created in step 1.
- On the VM, assign the new nic a static IP on that NAT subnet (e.g.
ip addr add dev ethX 192.168.0.100/24), and configure the default gateway to be the vSwitch IP, e.g. (route add default gw 192.168.0.1 ethX) - Add any nameserver to /etc/resolv.conf (
e.g. echo "nameserver 8.8.8.8" >> /etc/network/interfaces)
The effect of using the NAT interface is that the traffic coming out of any VM using the NAT vSwitch will be masqueraded behind the gateway IP (192.168.0.1 in my example), and will be re-routed internally using the routing table of the windows host. So, when I turn on the VPN, this will re-route all the Natted traffic to the VPN too.
There are many cases where I want to access the VM from the host directly, which the NAT makes difficult (everything will be behind 192.168.0.1). Rather than doing a bunch of dynamic port forwarding (which is also possible too with powershell), I've simply created another internal network between the host and the VM that is not NAtted (e.g. 192.168.5.0/24.
answered May 10 '18 at 8:35
init_jsinit_js
10627
I've managed to get something working on Windows 10, by creating a HyperV NAT interface. I believe you'll need windows 10 pro for that. Win10 home doesn't have Hyper-V (yet).
This has worked quite well:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network
- Create a NAT interface using powershell using the instructions in the link above. There is apparently a limit of 1 such interface according to the documentation, but on my computer there are currently 2 active vNAT interfaces: one I've created myself, and one called DockerNAT, which got created by Docker for Windows. This step will give you a new vSwitch, and assign it an IP on the host.
- In Hyper-V, edit the VM's settings to add a new network interface connected to the NAT switch interface created in step 1.
- On the VM, assign the new nic a static IP on that NAT subnet (e.g.
ip addr add dev ethX 192.168.0.100/24), and configure the default gateway to be the vSwitch IP, e.g. (route add default gw 192.168.0.1 ethX) - Add any nameserver to /etc/resolv.conf (
e.g. echo "nameserver 8.8.8.8" >> /etc/network/interfaces)
The effect of using the NAT interface is that the traffic coming out of any VM using the NAT vSwitch will be masqueraded behind the gateway IP (192.168.0.1 in my example), and will be re-routed internally using the routing table of the windows host. So, when I turn on the VPN, this will re-route all the Natted traffic to the VPN too.
There are many cases where I want to access the VM from the host directly, which the NAT makes difficult (everything will be behind 192.168.0.1). Rather than doing a bunch of dynamic port forwarding (which is also possible too with powershell), I've simply created another internal network between the host and the VM that is not NAtted (e.g. 192.168.5.0/24.
answered May 10 '18 at 8:35
init_jsinit_js
10627
edited Feb 27 at 0:33
answered May 10 '18 at 8:35
init_jsinit_js
10627
answered May 10 '18 at 8:35
init_jsinit_js
10627
answered May 10 '18 at 8:35
init_jsinit_js
10627
10627
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f911578%2fwindows-10-pro-as-a-nat-between-two-interfaces-to-route-vm-traffic-trough-a-vpn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Why NAT, which is something you want to avoid if at all possible? This sounds like a simple case for routing.
– Ron Maupin
Nov 19 '18 at 18:42
Maybe I don't need NAT per-se. I would normally bridge a virtual interface (which is on the same LAN as the VMs) to a physical interface, but then I'd be bypassing the VPN interface. That pulse secure VPN interface can't be bridged to anything, and by virtue of the VPN using a /32 as its address (I wish I could change it) means I also can't place anything in its subnet and use it as a gateway. It seemed that my only option was to make the VM traffic re-enter the host's routing table. I thought of NAT as a potential solution.
– init_js
Nov 19 '18 at 18:48
Right, you route between networks. You only use NAT when you must (private-to-public or overlapping network addressing). Bridging is what you do on the same network, but routing is between networks.
– Ron Maupin
Nov 19 '18 at 18:51