Claification on how to get GIT to work

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

Claification on how to get GIT to work

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 2:41 pm

Here is our setup. We both have COX cable internet connections. We both use Linksys BEFSX41 routers with the VPN disabled. We do forward the port (213) for GIT to a static IP address on our LAN network. We are also on the same IP segment his machines are 192.168.3.1-150, mine are 192.168.3.250-254 My router is *.*.*.254(DHCP disabled) his is *.*.*.1(DHCP enabled range 100-150) but his GIT machine is static. We also have Windows XP SP2 with the firewall disabled.

Within GIT we have UDP connections setup and they are up and connected. We are receiving incoming and forwarding packets (but they show it is invalid in the log), but we are unable to ping each other (ICMP is checked). Therefore non of our connection we try work, IE Battlefront, Joint Operations.

Within advanced GIT we have:
Ethernet II
Forward ARP
TCP
UDP
ICMP
Also Match Source Port
Don't Send Routable
Alt SourceIP (with our IP information in there)


Is there something we are doing wrong?
When using Linksys Routers do you forward the ports in the router and within GIT?
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm

Postby Ark » Sat Nov 06, 2004 2:55 pm

Why alter source IP? Unless you need to specifically use that for a hybrid GIT-broadcast internet-routable-unicast game setup like the WC3 example, you don't ever use that option just because you have NAT.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 3:06 pm

Thanks for getting back to me so quickly. I disabled the alter source ip. We are UDP up but still unable to ping each other, is pinging a good way to test whether or not GIT is functioning properly?
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm

Postby Ark » Sat Nov 06, 2004 3:13 pm

With UDP--UDP connections for GIT, the state is always "UP" since UDP is a stateless protocol. You must see if the connection status says it received anything or not. If not, what exactly does the error logs say for why its not receiving anything?
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 3:17 pm

I'm getting on my GIT Status:
"last packet forwared at Sat Nov 06 14:20:49 2004
last packet received at Sat Nov 06 14:20:49 2004"

This is what is showing up on the incoming log on my friends other end:
[Sat Nov 06 14:20:47 2004] 68.0.**.35: hw:**:84:00:c0:9f:0c invalid
[Sat Nov 06 14:20:47 2004] 68.0.**.35: hw:**:bb:00:0d:61:3f invalid
[Sat Nov 06 14:20:47 2004] 68.0.**.35: hw:**:bb:00:0f:66:92 invalid
[Sat Nov 06 14:20:47 2004] 68.0.**.35: hw:**:84:00:c0:9f:0c invalid
[Sat Nov 06 14:20:47 2004] 68.0.**.35: hw:**:bb:00:0d:61:3f invalid

Thanks
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 3:22 pm

This is what is coming out of our unforwarded log:

[Sat Nov 06 14:27:19 2004] network: hw:**:0f:66:0d:b9:41 EthernetII IPv4 UDP to:192.168.3.10:213 from:68.0.**.35:213 'wrong port number'
[Sat Nov 06 14:27:19 2004] network: hw:**:0d:87:b4:a0:33 EthernetII IPv4 UDP to:68.0.**.35:213 from:192.168.3.10:213 'wrong port number'
[Sat Nov 06 14:27:19 2004] network: hw:**:0d:87:b4:a0:33 EthernetII IPv4 UDP to:68.0.**.35:8767 from:192.168.3.10:1342 'destination is routable'
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm

Postby Ark » Sat Nov 06, 2004 3:33 pm

invalid in the incoming log is bad. Are you using different versions of GIT on each side? Try using the latest 0.99 beta for both sides.
For the unforwarded log, that is just based on the options you have checked - you have it set not to forward port 213, which is good since that would be forwarding GITs own traffic in an infinite loop, and you have it set not to forward routable traffic, so it will probably only forward broadcast or if the destination address is a 192.168.x.x address.

FYI, the hw: addresses can probably easily be guessed if you only blank out the first piece, since the first 3 pieces are just a code telling you the vendor of the NIC, the last 3 pieces are a serial number that they just increment. Not that it really matters, its not like people can use the hw address against you in any way.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 3:51 pm

Well we did notice my friend was using .99b2 and i was using .99b3. :oops:

Guess what the invalids went away and I can ping him!!!!!!!

Thank you so much with your timely responses. You have made great software.

Battlefront works!
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm

Postby Ark » Sat Nov 06, 2004 4:01 pm

For the record, from the post about 0.99 BETA 3:

http://forums.morpheussoftware.net/viewtopic.php?t=241

* Both the previous two will mean GIT no longer encapsulates a raw packet inside of a packet: GIT will introduce a small (2 byte) header between each packet to determine its length properly. This means 0.99b3 will not work with 0.99b2 and below properly - each side will spew garbage packets onto the network if used together.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Dark Knight -=B3=- » Sat Nov 06, 2004 4:14 pm

Thanks you for your time. My friend thought he had the newest version. We knew it would be something simple.
Dark Knight -=B3=-
 
Posts: 6
Joined: Sat Nov 06, 2004 2:22 pm


Return to GIT

Who is online

Users browsing this forum: No registered users and 3 guests

cron