- #Create a virtual network adapter windows 10 how to
- #Create a virtual network adapter windows 10 install
We have to see their computers using the IP addresses from the new subnet.
So, even with a secondary IP address on the interface, the VPN traffic doesn't work because the PCs on our side of the VPN see the traffic coming from their original (not the new) LAN subnet, and we cannot route using their original LAN subnet because of an IP address space conflict (which is why we needed a new subnet on their side to begin with). It seems that with windows while you can specify an interface to use with a static route, you cannot simply specify a source IP address directly on a static route. With one adapter and 2 IP addresses, the source IP for outgoing packets will always be the "primary" IP address of the interface used by the route, regardless of anything else. The reason why we need a second physical (or virtual) adapter here is because we need some sort of method of assigning the proper source IP address for the outgoing network traffic, so they can be addressed properly on the other side of the VPN. Mimiko wrote:Why using virtual adapter if you can assign another ip and mask to the phisical adapter? In windows an interface can have multiple IPs.
#Create a virtual network adapter windows 10 install
Is there a way to install a virtual network adapter to do this (using tapinstall, or some other tool) for windows? I suppose I could implement the same solution by installing a physical adapter on each machine, and wiring it up to the LAN, but obviously a software-based solution using a virtual NIC would be a better way of doing the same thing (without all the extra hardware and wiring)… I know that this solution will work, since I have done sort of the same thing using a virtual machine as a test on the foreign network… Simply by creating a secondary NIC on the virtual machine (this looks like a new physical adapter in the windows guest), putting it on the same virtual LAN, and assigning it to the new subnet, and targeting the route for that adapter, I was able to ping from one LAN to the other over the VPN (in both directions)… If I could create a separate, secondary adapter in windows and assign it to the new subnet on the physical network, then I can set up my persistent route in windows to target that interface, and that should resolve my source IP problems. Then I thought maybe bridging it to the physical adapter is what I needed to do, but that didn’t work either (bridging sort of does the opposite, and turns two separate network adapters into a single adapter with a single IP address/subnet on the bridge only)… I thought maybe somehow I could use the tapinstall provided by OpenVPN to create a virtual network adapter on the workstations, but as far as I can tell there is no way for me to simply tell the virtual adapter to attach itself to the physical network (even if I set the link status to always connected). The solution would involve installing a virtual/software based network adapter, to operate on the same LAN as the physical one… This way I can assign a secondary IP address to the secondary “adapter”, and set up a persistent route on the workstations to route traffic on that interface), which will make sure that the IP traffic being routed uses the proper source IP address for the return traffic.
#Create a virtual network adapter windows 10 how to
I posted about this problem a couple of days ago, but I think I may have posted it in the wrong place (I didn’t pick a proper sub-forum) and I have hit upon a solution that may work for me, so I wanted to ask about that here… For reference, if you want to see why I am asking for this you can read my other forum post here (rather than re-posting my issue I will just link it): Īnyhow, due to VPN routing and improper source-IP issues on a multi-homed network, I have found a solution that will solve my issues but I don’t know how to technically implement it…