CalliduS: Please demonstrate your set-up...

Gamer's Internet Tunnel, formerly Gamer's IPX Tunnel

CalliduS: Please demonstrate your set-up...

Postby Bubba » Tue Sep 28, 2004 8:01 pm

Hi!

You tease us with "We've got it working...", but no-one has actually written a half-decent description on how to connect two or more LAN's via GIT!

I can only assume that many viewers would greatly appreciate a quick run-down on how to set it up using probably the most common scenario of multiple LAN's, each behind a NAT-enabled router.

I'm mostly after "LAN-only" connections in games such as; BF 1942 and C&C Generals...


Some questions might be:

- Do you turn on a DMZ address/port on the NAT routers?

- Does each LAN need to use the same basic subnet? (i.e.: 192.168.2.x also, let's assume that we can avoid IP conflicts across the LANs)

- Does GIT need to know the actual IP address of each of the DSL modems (thereby, the routers) it's going to connect to?

- if your game is not listed, what ports do you forward?


Many Thanks!
Bubba
 
Posts: 4
Joined: Tue Sep 28, 2004 7:47 pm

Postby Michi » Wed Sep 29, 2004 1:01 pm

I need help configuring it too!!! I want to play with 2 friends of mine LAN-Only Games, so I opened the port, configured it somehow and when my friends try to connect my external IP they just got connection stats "UP", is it all OK?!
Michi
 
Posts: 2
Joined: Wed Sep 29, 2004 12:51 pm

Postby CalliduS » Thu Sep 30, 2004 4:49 pm

I'll try my best but I'm not great at detailing setup instructions.
Going on 2x LANs, both behind ADSL routers using NAT:

1. You need to first setup your LANs so they are both on the same IP range. For example if you have 5 PCs for each LAN then:

LAN1:
Router: 192.168.0.1
PC1: 192.168.0.2
PC2: 192.168.0.3
PC3: 192.168.0.4
PC4: 192.168.0.5
PC5: 192.168.0.6

LAN2:
Router: 192.168.0.21
PC1: 192.168.0.22
PC2: 192.168.0.23
PC3: 192.168.0.24
PC4: 192.168.0.25
PC5: 192.168.0.26

2. Install GIT on 1 PC on each LAN. I used GIT 0.99 beta2. Doesn't matter what PC, so long as the router can port forward to it.
3. Run GIT, goto config and add the external IP of the LAN you wish to connect to and set the port to 213 with the connection method as UDP - Fastest. Make sure you do this to both GITs.
4. Add the ports for the games you wish to link, i.e:
5555 : Codename Panzers
6112 : Warcraft III
8080-8099 : Generals (did a range as I didnt have time to check the port but I think it just uses 8080)
18321 : Medieval Total War
34987 : Rise of Nations
I also added the DX8 games ports

5. Goto Advanced config and tick only these settings:

Ethernet II

Forward ARP

TCP
UDP
ICMP (got this ticked so I can test ping IPs on the other LAN)

Also Match Source Port


6. Via your router admin, forward port 213 on UDP to the IP of the PC running GIT. Do the same on the other LANs router.

That should be it.
To test you could try pinging an IP from the other LAN.
I have tested GIT with all of them games listed above in the config port bit and they all worked fine.
If you want to add a LAN3 then just do the same but when entering the port for the connection where you enter the host IP, make sure its on a different port number.

LAN1 - LAN2 = 213
LAN2 - LAN1 = 213

LAN1 - LAN3 = 214
LAN3 - LAN1 = 214

LAN2 - LAN3 = 215
LAN3 - LAN2 = 215

Hope this helps you all. Just hope I didn't miss anything out.
Like I said before, this works for me and works damn fine. Thanks to Morpheus Software for making this nice program.
Last edited by CalliduS on Thu Sep 30, 2004 5:06 pm, edited 2 times in total.
CalliduS
 
Posts: 34
Joined: Sat Sep 18, 2004 3:33 am
Location: UK

Postby CalliduS » Thu Sep 30, 2004 5:03 pm

Oh also for finding out the ports for the games, try google searches and read the readme.txt that come with game installs. They often say about ports that need to forwarded when playing behind a router.
When using GIT to link LANs though, there is no need to do any port forwarding with the router, other than the GITs port. GIT its self will forward the ports you want it to.
I found games to work even if the PCs on the LAN don't have a gateway to the net as it seems all the traffic goes to the GIT prog, then tunneled through that 1 port.
Another way to find the ports used is to install a porg like Net Peeker (google search it). Run the game on 2 local PCs then flip back to windows on the host PC to see what port it uses to host on.
e.g in net peeker under the the game its self you will see for say Panzers:

192.168.0.2:5555 <-- 192.168.0.3:1243

192.168.0.2 being the host, you can see that its using port 5555.
Some games use DX ports though and this can change each time a game is hosted. Thats why I just forward all the DX8 ports 2302-2400.

I don't claim to be very clever at this and I have only got it working through trial and error, so I might not be able to help you if your setup is different to what I did.
CalliduS
 
Posts: 34
Joined: Sat Sep 18, 2004 3:33 am
Location: UK

Postby Ark » Thu Sep 30, 2004 5:16 pm

That is a very informative post. The only thing I would add is that if you have GIT installed, you can easily use WinDump (the windows port of tcpdump, a common Linux packet sniffer). WinDump is available from the same people who make WinPcap, at http://windump.polito.it/
Its a command line utility, you just run it by typing 'windump' at the command prompt assuming you are in the right directory. You can use windump with parameters like 'windump not port 213 and not port 110 and not port 80 and not port 53 and not port 137 and not port 138 and not port 139' so that it doesn't display GIT traffic(213), POP3 traffic(110) from your mail program, web traffic (80), DNS traffic (53), or NetBIOS junk (137-139).
Also, you can use the GIT logging options to find out what ports are used if you want. Set GIT to forward nothing, then check the logging option to log unforwarded packets, and everything will appear in the text file unforwarded.log in the GIT directory.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Subnets and non x.x.x.1 router IP's

Postby Bubba » Thu Sep 30, 2004 9:03 pm

Hi!

Thanks for the tutorial, it makes sense now!

I can only assume that a lot of games need for each participant to be on the same common subnet for the "lan" setting to work with any regularity.


But, when you revise your router gateway to an non-192.168.2.1 address, do you need to change the subnet mask?

For some odd reason I can no longer reach my router, even though everything works fine with the newly applied gateway address.



Thanks.
Bubba
 
Posts: 4
Joined: Tue Sep 28, 2004 7:47 pm

Wups! What about "Alter source IP (for NAT)"??

Postby Bubba » Thu Sep 30, 2004 9:40 pm

Well, we followed your directions to the letter, but we can't ping eachother... :(


You don't make any mention of the "Alter source IP (for NAT)" setting.

You said your set-up uses two LANs, each behind a NAT, then why would you not use this setting?




Thanks.
Bubba
 
Posts: 4
Joined: Tue Sep 28, 2004 7:47 pm

Postby Ark » Fri Oct 01, 2004 12:31 am

In this particular example, he was saying you all need to be on the same subnet. This means you must all have the same netmask and same host portion of your IPs.
If your netmask is 255.255.255.0 and then your host portion of the IP is the 192.168.0
you must all have 192.168.0.x IPs then.
He used 192.168.0.1-6 on the first LAN, and then 192.168.0.21-26 on the second LAN. Notice that both are in the 192.168.0.0/255.255.255.0 network and no IPs conflict, not even the router on each side.

The Alter source for IP is only useful if you want packets that are actually coming from your internal LAN address like 192.168.0.2 to "appear" to be comming from your external address like 24.50.100.200.
Since the goal of this example was to make 2 physically separate networks appear as 1 virtual network using GIT, having packets appearing outside that virtual network is useless.

The point of the alter source IP for NAT option is mainly to be used in conjunction with the don't send unicast option, so that you only tunnel multicast packets. This is a completely different GIT setup, one that is known to work with WC3 for example, since multicast packets are never routed over the internet, if you tunnel them in GIT, you can locate the WC3 server and connect directly to it. If you are using NAT, these multicast packets will appear to come from your internal 192.168.0.2 IP and any client trying to join your WC3 server will be trying to connect to a non-routable private LAN address. Altering the source IP will make that multicast packet appear to come from a different address, so that the clients will try to connec to that IP instead. With this setup you would have to forward both port 213 for GIT as well as the game port (6112 for WC3) from your external IP to your internal LAN IP.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby CalliduS » Fri Oct 01, 2004 1:43 am

Bubba, only tick the options I stated. Don't alter the IP. Spend a bit more time setting up each LAN and making sure they work 1st before connecting them with GIT.
Also try installing Net Peeker on the PC running GIT. It will list the GIT program in its list and if you double click it, it will show if there is a connection from the other LAN like this:

localhost:213 <-- LAN2-external-IP:213

If this is showing on both PCs running GIT then there is a tunneled connection and you should be able to ping the other LAN and play games on the ports you added in GITs config.
CalliduS
 
Posts: 34
Joined: Sat Sep 18, 2004 3:33 am
Location: UK

Postby Michi » Fri Oct 01, 2004 11:35 am

CalliduS wrote:2. Install GIT on 1 PC on each LAN. I used GIT 0.99 beta2. Doesn't matter what PC, so long as the router can port forward to it.
3. Run GIT, goto config and add the external IP of the LAN you wish to connect to and set the port to 213 with the connection method as UDP - Fastest. Make sure you do this to both GITs.


Do I have to enter the Router external IP or which one? And what does the host do? Do you need even a host?

We both have a Netgear Router, I have internal ip 192.168.0.5 and he 192.168.0.2... I want to host, has he to connect to my external IP then? Thx in advance
Michi
 
Posts: 2
Joined: Wed Sep 29, 2004 12:51 pm

Postby Ark » Fri Oct 01, 2004 11:43 am

Michi - there is a difference between what people are talking about here.
One connection is the GIT connection, the other connection is the game connection.
GIT must always connect to external IPs and if you use NAT, port 213 must always be properly forwarded to the computer running GIT.
Beyond that, it depends on the type of setup you are trying to accomplish. If you are creating 1 virtual LAN out of 2 physical LANs, everything else will involve internal IPs and absolutely nothing can conflict. Even if your IP is 192.168.0.5 and his is 192.168.0.2, if you both have your gateway router's IP set to 192.168.0.1, there is a conflict.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby CalliduS » Fri Oct 01, 2004 4:18 pm

This is my setup apart from I've changed the "host or IP" field to "lan2_external_IP" as I don't wish to show the IP I'm connecting to. Just change this to the external IP of the other LAN. On the other LAN do the same but put your external IP in.


Image

Image

I can't make this anymore simple than what I've said and shown. Hope you get it working.

BTW, if the above imgs dont show, its because I sent them to photobucket and its got a rubbish bandwidth limit.
CalliduS
 
Posts: 34
Joined: Sat Sep 18, 2004 3:33 am
Location: UK

Postby poseyjmac » Fri Oct 29, 2004 11:01 pm

is 'forward ARP' necessary for this to work?
poseyjmac
 
Posts: 42
Joined: Mon Mar 29, 2004 11:33 pm

Postby Ark » Fri Oct 29, 2004 11:45 pm

I noticed that ARP was required for AOM to work properly, so others may require it as well. ARP is very important if you want both sides to really think the LANs are truely one single LAN.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm


Return to GIT

Who is online

Users browsing this forum: No registered users and 25 guests

cron