Originally Posted by Shiftstealth
I suppose, but trying it at the windows level sounds...strange. I mean i guess i'm just more familiar with cisco devices. I mean i understand what beers is getting at with the policy based routing, but i don't think windows has any functionality for it. I mean you are essentially talking about a layer 4 router. Even then it isn't the same NIC.
I mean this *might* be possible if you do the million or whatever it would be ROUTE ADD (IP ADDRESS) MASK (mask) in cmd, but it would be a ton of effort.
I don't think it's as difficult as you're making out. Windows 7 would have the same NT subsystem as the Windows Server range and it's definitely possible to do on Windows Server.
Plus route add
supports subnet masks so you wouldn't need to add every IP in there. Just set the VPN subnet route on the second NIC (with the VPN listener on that IP) and set the first subnet to be the default route. With any luck, you wouldn't need a layer 3 switch as you could just set your router to work on a wider subnet:eg router config:
LAN == 192.168.0.0 255.255.0.0
192.168.1.0/24 == ethernet, WiFi, etc
192.168.2.0/24 == VPNThen on the PC:
NIC 1 == 192.168.1.2 (default route)
NIC 2 == 192.168.2.2 (VPN)
VPN config == listen ip: 192.168.2.2
I'm not a networking guy though - so I make no guarantees that the above would work.