Age of Empires III - need help!!!

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

Age of Empires III - need help!!!

Postby tr1ad » Mon Mar 27, 2006 6:04 am

hy folz,

we are trying to get AOE III to work over GIT, but we failed.
My friends PC is connected directly, so I think he has no problems with that, so we decided that he will be the host and I will be the client.
GIT is running on both PC's.
My PC is connected through a D-LINK DI-624+ router.
I used following portforwarding settings:
http://www.portforward.com/english/rout ... es_III.htm

In the GIT config we used following settings (as recommended):
http://s94178705.onlinehome.us/tazeat/git.html

But it doesn't want to work.
So we tried to config in GIT "Forward which TCP/UDP ports" with following settings "217-65535 : All the rest".
But this also does not work.

I will post some logging entrys which I found under "unforwarded.log":
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 TCP to:84.162.76.226:213 from:192.168.0.110:3189 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 TCP to:84.162.76.226:213 from:192.168.0.110:3189 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:48 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 TCP to:84.162.76.226:213 from:192.168.0.110:3189 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 TCP to:84.162.76.226:213 from:192.168.0.110:3189 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 TCP to:84.162.76.226:213 from:192.168.0.110:3189 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:0 from:192.168.0.110:2300 'destination is routable'
[Mon Mar 27 14:09:49 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.76.226:2300 from:192.168.0.110:2300 'destination is routable'

...

Does someone know hat "destination is routable" means in this context?

I read in another post that for act of war GIT will work with the same settings we used instead of using "UDP Fastest" and not "TCP connect".

Thanks in advance for all hints!!!

greetz
tr1ad
tr1ad
 
Posts: 6
Joined: Sun Mar 26, 2006 2:00 pm

Postby tr1ad » Mon Mar 27, 2006 6:23 am

I will post some more informations about our IPs:
Client IP: 192.168.0.110
Router IP: 192.168.0.1
My external IP: 84.56.175.17

Host IP: 192.168.0.5
External IP of the host: 84.162.76.226

Both on Subnet: 255.255.255.0

Config in GIT:
Ethernet II
Forward ARP
Zlib Compression
TCP
UDP
ICMP (probably not needed)
Also Match Source Port
Don't Send Routable.
tr1ad
 
Posts: 6
Joined: Sun Mar 26, 2006 2:00 pm

Postby Ark » Mon Mar 27, 2006 10:10 am

It means that particular packet is not tunneled, because you checked the "Don't Send Routable" option, and the destination address of those packets (84.162.76.226) is a routable internet address, so the packet should be able to reach that destination without GIT's help.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby tr1ad » Mon Mar 27, 2006 11:55 am

thanks for the info ark, but without checking this option it also don't works. any idea why?
tr1ad
 
Posts: 6
Joined: Sun Mar 26, 2006 2:00 pm

Postby tr1ad » Mon Mar 27, 2006 12:07 pm

Now we tried to grab another port in the config of GIT.
After we identified this entry in the log
[Mon Mar 27 20:28:52 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.111.48:213 from:192.168.0.110:213 'wrong port number'

we tried to use port 214, but then this message occurs:
[Mon Mar 27 20:37:16 2006] network: hw:00:11:2f:ac:44:a8 EthernetII IPv4 UDP to:84.162.111.48:214 from:192.168.0.110:214 'wrong port number'

We both used port 214, what have we done wrong?

Do we need the TCP listen server when we use the method "UDP - fastest"?

We tried with and without the TCP listen server but again it does not work.

Thanks in advance!
tr1ad
 
Posts: 6
Joined: Sun Mar 26, 2006 2:00 pm

Postby Ark » Mon Mar 27, 2006 12:30 pm

I think you are missing the point of the logs here. The unforwarded.log is not an "error report" of problems you are having. It is a list of every possible packet that GIT saw on your network as being available to forward, but choose not to because of the options you have set. In this specific case, you aren't tunneling port 214, which is a *good* thing, otherwise you would be tunneling GIT's own traffic into itself in an infinite loop!
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby karma » Fri Mar 31, 2006 8:57 pm

tr1ad!

checkmark 802.2 also in the advanced config.

are you using tcp connect/listen? or udp? In either case, on the tcp listener's router, port 213 must be forwarded to the GIT computer's private IP.

try it that way, both of you with 802.2 checked, and the host having port 213 forwarded.
karma
 
Posts: 69
Joined: Mon Mar 14, 2005 7:42 am
Location: yokosuka japan


Return to GIT

Who is online

Users browsing this forum: No registered users and 29 guests