Page 1 of 1

What Are We doing wrong - GIT setup

PostPosted: Tue Feb 10, 2004 5:48 pm
by Clintski2
A Friend and I would like to link or LANS using GIT over the Internet via ADSL we have the following setup.

SITE A
router External IP=a.a.a.a
Router Internal IP=192.168.1.2
PC Running GIT On Local LAN =192.168.1.3

Trying to connect to :-

SITE B
Router External IP=B.B.B.B
Router Internal IP=192.168.1.50
PC Running GIT on local LAN= 192.168.1.51

We Have both put Port 214 to be forwarded to our local LAN PC's Running GIT into our respective routers in the NAT/Virtual Server settings.

But despite trying various setting in GIT We have so far failed to be able to even ping the opposite SITE's PC's

Would someone be so kind as to give me a definitive settings guide that I need to set in the configuration and advanced config settings in GIT to get the link up and running.

Help would be much appreciated.
Clintski

PostPosted: Tue Feb 10, 2004 6:55 pm
by Ark
Does GIT say its connected or not in the Connection Status ?

Are you even forwarding ICMP?

Are you using the adjust source IP for NAT option?

PostPosted: Thu Feb 12, 2004 3:11 pm
by Clintski2
b.b.b.b:214 (tcp connect) - UP since Thu Feb 12 21:24:54 2004
last packet forwarded at Thu Feb 12 21:29:32 2004
last packet received at Thu Feb 12 21:29:32 2004



ICMP is set to forward as is tcp and udp

ip v4 forward options ONLY if broadcast - unchecked
Alter source ip for nat ticked
192.168.1.3 internal to external IP of local router

Should both the a.a.a.a site and b.b.b.b site local lan pc be on the the same subnet ie mine are currently 192.168.1.1->49 the b end's are set set 192.168.1.50->100 SNM= 255.255.255.0 both ends

Thanks for replying...

PostPosted: Thu Feb 12, 2004 3:16 pm
by Ark
For what you want, it sounds like you should not be using the alter source IP option. That option is mainly for running a server behind a NAT where you only want to forward broadcast packets and have the non-broadcast packets routed directly through the internet without GIT as in the case of WC3 for example, where the clients will connect to the source IP address that the broadcast packets are coming from.

PostPosted: Thu Feb 12, 2004 3:27 pm
by Clintski2
Ok. I See, ....I think...

So for pc-pc turn NAT option off and then ....

Should I be able once connected - to... ICMP Ping from my pc 192.168.1.3 across the TUNNEL to ping 192.168.1.51 ?

PostPosted: Thu Feb 12, 2004 3:56 pm
by CyberVenom
With NAT off and "Only boradcast" off as well, pings should be tunneled.

PostPosted: Thu Feb 17, 2005 2:30 am
by Archie
Well, it seems we have the same setup (except that one side is a Wireless LAN), but even ping does not work! Playing Joint Operations neither. :roll:

We forward everything via UDP-Fastest, IPv4 (TCP/UDP/IMCP). Also, NAT is off, and 'Don't send broadcast' also. However, the connection status window shows we are receiving.

In our incoming logs we see both as well the NAT ip's as the external ip's, but a ping to the local address (192.168.x.y) of the other side does not work.

Is there an issue we overlooked? We've been struggling with it for several hours now. :shock: