I found why udp aint workin right...

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

I found why udp aint workin right...

Postby taz_eat » Tue Oct 12, 2004 7:11 pm

I found why udp aint workin right...
in invalid connections I got this tons of times:
[Tue Oct 12 18:07:18 2004] 67.168.92.*: wanted:67.168.92.* got:192.168.0.100 'incoming UDP packet denied'

What is that?
(his local is 192.168.0.100 and external is the 67. one)
* is put just cuz i dont know if he want his ip publically known
Last edited by taz_eat on Fri Oct 15, 2004 4:40 pm, edited 1 time in total.
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Tue Oct 12, 2004 7:50 pm

This means you have something set up very wrong. GIT expects you to enter the external IP address of the opposite computer running GIT (and thus forward port 213 from the external address the actual internal one with GIT, if you need to, by adjusting settings in your router, not GIT)
GIT only accepts UDP packets on the port 213 from the address you listed, so if the packet to GIT on port 213 is not from 67.168.92.(?) then GIT just ignores it.
You are somehow getting packets from 192.168.0.100 to GIT on port 213. The source address of the packet from his computer should be 67.168.92.(?) if his NAT is set up properly. None of these addresses, translations, or port forwarding are things you can set in GIT, they are things to set in your routers.
Of course, if you are tunneling port 213 in GITs setup, maybe by selecting something like all ports 1-65535 or something, then you will create an infinite loop of GIT forwarding its own traffic inside a new tunnel and thus all these dropped/denied packets.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Tue Oct 12, 2004 7:56 pm

So he can set this with his router?

We have tried just forwarding upd 60010 or 213 (tried both... to see if isp is interfering... it wasnt), as well as using dmz. that was with dmz.

edit:
Using packet sniffer while he is on just port forwarding the packet header is from his and i dont get an invalid just nothing works :( ping, etc. it does say in connection status
67.168.92.*:60010 (udp) - UP since Tue Oct 12 18:17:43 2004
last packet received from 67.168.92.*
last packet forwarded at Tue Oct 12 19:26:51 2004

but that is it.


edit 2: Pissed so I screenshotted EVERYTHING... (large dialup users may want to turn back now).

My config:
Image
his config:
Image
my advanced: (device is lan nic not internet nic)
Image
his advanced:
Image
my router:
none, direct connection with another comp on 2nd nic connected to me.
his router:
Image
Tiny firewall's connectin list:
Image
My Commview inbound packet:
Image
My Commview outbound packet:
Image


When pinging constantly to his local address (192.168.0.100) this is in forwarded.log repeatedly:
[Tue Oct 12 19:56:39 2004] network: hw:00:0e:a6:6e:2b:f6 EthernetII ARP request to:00:00:00:00:00:00 from:00:0e:a6:6e:2b:f6(192.168.0.254) for:192.168.0.100 'ok'

In the connection status i have this:
67.168.92.*:213 (udp) - UP since Tue Oct 12 19:48:59 2004
last packet forwarded at Tue Oct 12 20:21:57 2004
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Tue Oct 12, 2004 10:41 pm

I don't see why he is forwarding ports you are not in the normal GIT config window, but otherwise the setup is fine.
I assume you are both on 192.168.0.x/255.255.255.0 networks and no internal IPs conflict between your two LANs? Not even your routers?
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Tue Oct 12, 2004 10:44 pm

yup. no ip conflicts. both in 255.255.255.0 subnet. he was using those extra ports cuz we tryed nfl madden 2k5.

But i think we are gonna try a vpn, seems much easier... he went to bed il try tomorrow wit that :(.

its like i recieve the git to git packet but git just ignores it. it doesnt even put it in invalid connections :(.

(note it put it in invalid connections when he was on dmz as it kept the 192.168.0.100 in header and git threw it out.)
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Tue Oct 12, 2004 11:33 pm

Can you ping from your 192.168.0.x IP to his 192.168.0.100 IP? With ARP+ICMP that should work, unless you have an IP conflict or additional IPs not in the 192.168.0.x subnet bound to the same computer.
Do both sides connections list like:

127.0.0.1:213 (udp) - UP since Tue Oct 12 22:31:10 2004
last packet received from 127.0.0.1
last packet forwarded at Tue Oct 12 22:31:36 2004
last packet received at Tue Oct 12 22:31:36 2004

(obviously not 127.0.0.1 or the same date/times)

You listed 67.168.92.*:60010 (udp) - UP before - why is GIT listening on port 60010 and not port 213?

Both GITs should have all 3 "last packet" lines listed if anything was successfully sent via the tunnel.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Tue Oct 12, 2004 11:52 pm

In the connection status i have this:
67.168.92.*:213 (udp) - UP since Tue Oct 12 19:48:59 2004
last packet forwarded at Tue Oct 12 20:21:57 2004

Nope i went ping -t 192.168.0.100 and he went ping -t 192.168.0.254 a left going for like 3 hours while we were testing... (Tons of arp requests were forwarded..)

Oh and we were trying different ports... we used 213 and 60010 niether worked.

note with tcp settings ping worked and it showed both forwarded and sent.


im going to bed now but il check back tomorrow.
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Wed Oct 13, 2004 2:08 am

If TCP connect + TCP listen works for GIT on port 213 but UDP does not, then one side does not have the port forwarding in their NAT router set up for port 213 properly.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Wed Oct 13, 2004 3:35 pm

Ok il make sure of that, Il have him run commview and see if he recieves my stuff. But i think when he ran it before he did, I will have to ask him when i talk to him next.

Another question that could be the answer which i just thought of,
Does git use winpcap to capture the incoming udp or does it just recieve it from openning the port listenning without using the capture driver?

Because since I have 2 nic's:
1 for net
2 for other comp on lan (direct connection using crossover cable)

I have git set to the second nic in advanced that I have my other comp on, is that bad?
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Wed Oct 13, 2004 5:06 pm

For the GIT--GIT connections on port 213, GIT just uses normal WinSock sockets, not Winpcap.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Thu Oct 14, 2004 11:18 pm

Well after much more testing we found out using commview he is recieving packets.

We also found out that even if he uses tcp server i cannot connect to him.

He can connect to me if i am tcp server.

It is not his firewall.

He seems to have set up his router correctly as he is connectable on bittorrent or other things that require incoming ports.

This sucks.

...Oh and the thing that it uses winsock thats what i thought. I didnt think that was the problem.
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby Ark » Fri Oct 15, 2004 2:55 am

From what you say, if you cannot connect to him when he uses tcp server, then he either is not forwarding ports through his NAT, or he has a firewall in the way. There is really no other choice. Especially if he can connect to you using TCP.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby taz_eat » Fri Oct 15, 2004 4:38 pm

yup. Its just so wierd though because commview shows him recieving packets. thefore router cannot be problem. and he has disabled all firewall stuff. ids/firewall (windows firewall has never been enabled :) ). BUT one thing we did notice is my outgoing packets to him that commview detected was not the same as the incoming packets that he got. Im not sure if that is anything or not, but w/e. we will see later i was gonna try having his router log dropped packets and stuff later.
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm

Postby taz_eat » Mon Nov 15, 2004 9:58 pm

11/15/2004 (srry for double post but this is worth a bump)

UDP WORKS NOW. HE UPDATED HIS ROUTER FIRMWARE!
sigh.... i told him to do that before he didnt listen...

I think where it goes wrong is on udp packets it changes the port info so git threw them out... but it worx now! with dlink routers UPGRADE ur firmware!
taz_eat
 
Posts: 15
Joined: Thu Oct 07, 2004 11:46 pm


Return to GIT

Who is online

Users browsing this forum: Google [Bot] and 24 guests

cron