Newbie Wingate VPN Question

[golson]

Hi Everyone,

I'm currently evaluating wingate, and have a question as to it's capability. Forgive me in advance, as I'm not a routing expert, and am fairly new to wingate VPN.

My configuration is as follows:

wingate VPN server is XP machine, local IP address 192.168.1.102. I have successfully configured this, and am able to connect in from the outside world into the this server via wingate VPN client, and can browse exported files on the server, etc.

I also have a linux machine on the same network as the wingate VPN server. It's IP address is 192.168.1.7. I have not yet been able to even ping this machine from the outside world. I have set the local participation of the VPN server to Local network, assuming that requests would be forwarded to the local network via the wingate VPN server.

Do I simply need to add a route back from my linux machine to the wingate VPN server to get things going, or am I going about this the wrong way?

Many thanks for any suggestions.

Cheers,

--Greg

[Pascal]

Hi Greg,

Is your Linux machine set to use the WinGate Server as it's default gateway ?

You're close in that it is a routing issue you need to resolve here. The problem is that the Linux machine does not know about the remote subnet. So it will receive packets routed from the VPN Node, but will not know where to send them back to.

There are three ways we recommend for this:

1. Setting the default gateway to the VPN Node. This applies if you are also using it for connection sharing, etc.

2. Install a RIP v 2 compatible listener on the client PC(s)

3. Set a static route on the client PC that will push all traffic to the remote subnet through the VPN node

They're listed according to ease of use, but any of the three should get you going.

[golson]

Thanks for the quick response, Pascal.

To answer your question, no I have not set the VPN server as my gateway on the linux box. Guess that explains why pings and such fail.

I think option #3, though a bit more involved, might be the proper way to proceed for me. I'd like to go with option 2, but am not sure that a rip 2 compatible listener exists on linux (does it? perhaps it does...)

Option #1 would work, but in certain cases, the wingate server machine may not be online, and I would still like to have internet access from the linux box in that case.

I'll give option 3 a try in the next day or two, and see how things go.

By the way, how many licenses would I need in this configuration? I figure I would need one for the VPN server, and one for the remote VPN client. Would I need a third for the linux box, since it's acting as a VPN participant?

Thanks again for the suggestions.

Cheers,

--Greg

[MattP]

Hi Greg,

I just sent you an email through the support system which should answer your questions, but anyway.....you'll need a license for each concurrent VPN participant, in your case you'll need a 3 user license for your LAN and a single user license for your remote machine. If you have a remote LAN that is accessing the VPN then you'll need as many licenses as you have machines needing to connect at the same time.

Regards,

Matt

[golson]

Just a quick followup: routing to the wingate server works just fine.

I did find a rip2 compatible client for linux which may work; it's called zebra (www.zebra.org; does a lot more than rip). I'm going to give it a whirl in the next day or two to see if I can avoid routing back through the wingate server machine.

Many thanks!

--Greg

[golson]

One final follow-up for anyone who might be interested; the zebra/ripd worked just fine on the linux box.

For anyone looking for a linux rip2 solution, you might want to look at zebra.org.

Regards,

--Greg