Gaming over VPN

[mandrake_lord]

im trying 2 set up a vpn with xx amount of comuters over the internet for gaming. i can do this over the basic widows vpn stuff but that 2 networks only, i want to play all my games with my friends without hauling our pcs in 1 location and laning it up. now with my trial and error skills i have learnt how 2 use the wingate vpn software on a basic level. i have a server which all my friends can join, and we can share files 2 but i create a lan game (warcraft 3 tft) for example and none of them can see the game if they host i can't see their game either. im using windows xp home and im going through a router which has a fire wall built in, i usually leave that disabled. does anyone know why we can see eachother in wingate and in network neighbourhood but not in the lan games lobbys???!!! many hours have been spend on this

[Pascal]

If you go to ENS, you will find a "UDP Relay Broadcast" setting. If I remember correctly, it's on the "Routing" page. Add the port number for WarCraft III here (The one it uses for announcing the server status)

What's happening is, you have 2, 3 ... (x) networks connecting in to the server from different 'subnets'. When your host announces it's game, that's on the local subnet. For that information to travel across the VPN, you need to tell the ENS that it should relay broadcasts for that port number. (So, you'd need to do this on each node that would potentially act as the host).

Most of our original testing or this feature was done with WarCraft III.

[mandrake_lord]

Thankyou that helps soo much, now i was wondering if i host a game of Dawn of war or warcraft 3 if all the people can join it. if so can a user on my vpn host a game and the others join or am i going to have 2 host evry game?

[Pascal]

When you say "user on my vpn" are you talking about a client computer on your network?

If yes, the answer is YES if that machine can actually participate in the VPN. (Copy files, etc.)

[mandrake_lord]

Some of my clients on my vpn. in published routes, it sez behind NAT/ translated. below it sez an ip and a gateway then (in conflict) this seems to be the DSL clients only. also some of my clients are on my vpn but their pcs are not listed in microsoft networking tab. and some that are say (testing constantly) can you provide any information

[Pascal]

Phew. That is going to be an involved discussion. WinGate VPN is a routing based solution. For that to work, you might need to do a few tweaks to your setup.

For example, if you have two networks (VPns) in the 192.168.1.x range joining in: when a packet is destined for 192.168.1.5, which network does it belong to?

This is most easily solved by renumbering your networks so that everybody is on a unique subnet range. Another way is to setup static routes, so that the VPN Node knows that 192.168.1.5 belongs to network X, while 192.168.1.6 belongs to network Y. That is signfiicantly more complex.

I'd recommend that you read our VPN Setup guide. It will take you through most common configuration steps and should make this a lot easier. You can find it under our white papers section under support.

(http://www.wingate.com/files/VPN_Setup_Guide.pdf)

The in-document links don't work currently - but you will still be able to use the document. This guide to routing is always a good read.

http://www.wingate.com/files/routing_paper_letter.pdf

[mandrake_lord]

Thats kinda confusing but i think i got it. some of my clients pc's are appearing in eachothers lists. 1 of them joined my DOW game b4 and the other 1 could not, this person was also in conflict. now the person who was in conflict is not and he is able 2 join games and the other is not. im assuming we all need different local ip addys. do we all need if digits in 192.168.1.xx or in 192.168.xx.1.

[Pascal]

As soon as you see routes that are marked as "In Conflict" that's WinGate VPN telling you that it does not know how to deal with that problem. Read the document on routing. It's very educational and well written and will definately help alleviate some of that confusion.

Basically, everybody needs a different internal subnet. So, make it like this:

VPN client 1's network:
192.168.10.xxx

VPN client 2's network:
192.168.20.xxx

VPN client 3's network:
192.168.30.xxx

etc.

[mandrake_lord]

sweet i think i got this down now. thankyou tonz for your time :D everyting is going good