11 replies
by mckaytech
You are proposing a network setup I've not seen before so I'm not certain of how it would work. The best answer will probably depend on such factors as where the VPN tunnel ends (on your desktops or on your server), what VPN client you're using, whether users will want to access the Internet while having the VPN tunnel up, and what OS you're running on the desktop.
Without that information, my best guess is that this is going to be a tough implementation, particularly if you are going to berunning the VPN client on the desktop. However, if the VPN tunnel terminates on the server, it's a fairly routine routing issue and would not require the workstations to have multiple NIC cards.
Hopefully, another forum participant will have better information on this particular setup but I would also be glad to take another look with more information.
regards!
paul
by jgwynn
by mckaytech
I hope someone else can prove me wrong, but I don't think your proposed solution will work. If you have a situation where users would not be simultaneously accessing the VPN and the local network, you would just point the default gateway on the PC to the ISDN router and the VPN client to the Instagate box. No need for multi-homing but they would have to close the VPN, open the browser, etc.
However, based on what I know about VPN clients, there is no way to separate packets at the application level and say "okay, http to the right and vpn to the left". When the VPN client is up and running, ALL packets go through the tunnel (that's the P in VPN).
In particular, since Win98 doesn't natively provide a routing capability, it would require third-party routing software and I don't know of any that would work with a VPN client.
NT Server does have IP routing but without implementing Proxy Server or something similar, I'm not sure how you would direct packets of one type to one interface and all the rest to another interface.
The bottom line is that with the VPN client up and running on the desktop, your users won't be able to access the Internet at all. If they can, your VPN isn't private after all.
And that brings upthe other issue and that is that your application vendor might not appreciate the irony in establishing a VPN to a network which is then open to the Internet on the other side.
That's kind of how Microsoft got hacked a few weeks ago.
regards!
paul
by jgwynn
by brian_e
It has nothign to do with which connection is made first.
It is 100% related to your routing table and default route.
On Windows 2000 you would use "Route Print" at a command primt to display your current route tables.
Take a look at this before and after each connection is made.
Regards,
Brian
by jgwynn
by tomjockers
Assuming you don't have a proxy connected to the ISDN which you could manually point a browser to for web browsing (the best solution).
You can use the ISDN, as the default router then all traffic will try that route first.
Most VPN's will force all traffic through the VPN. Meaning the users will have to close the vpn to browse the Internet or any other local network resource.
Additional Info required
OS of Workstations?
Are there any servers?
OS of Servers?
Which VPN and which version?
(i.e. Novell, Microsoft, Cisco)
by jgwynn
This one is fairly straightforward:
Set the default route on the workstations to the ISDN router. All IP traffic destined to somewhere other than your local network will go to the ISDN router. Then, it's up to the router to send the packet to thenext hop.
If you are using a VPN client application on a Win32 box, the VPN client will either 1)establish an IP address for itself when launched or 2) use the primary interface on the PC. If your VPN client is capable of having its own IP address, then give it a permanent address on the segment that the vendor requires. When launched, the address of this interface will be known to the OS and traffic destined for the server on the VPN segment will automatically be routed through the VPN interface. All other traffic will still go through the ISDN router. If you are not implementing routing capabilities on the Win32 client box, then you won't have any security issues between the VPN network and the internet to worry about.
If the VPNclient uses the primary interface on the Win32 box, then the IP traffic from this box will go to the ISDN router. So, you will need to make the ISDN router aware of the VPN network by adding a static route. It doesn't sound like this is the case so,I think the scenario above will solve your problem. In either case, you don't need to multihome your client machines.
by jgwynn
by jgwynn
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending