Page 1 of 1

GIT is closing (or blocking) my net connection !!! why ?

PostPosted: Sat Nov 27, 2004 4:00 pm
by distance
Hi I have problem with GIT...

Whenever I start it and my friend connects to me GIT-GIT for some game playing GIT closes my internet connection.
(I cannot browse, ICQ not working.... till I exit git and restart my network connection)...

Is that normal ?
I think not, cause he doesn't have same problem, his connection is working flawlessly...

Could the problem be that I have wireless card for internet connection ?
Maybe winpcap 3.0 has some problems with may Z-COM WiFi card.

The same thing happens when I connect to him with my Win XP VPN client... (it's like private tunnel)

any ideas ?
thx!

PostPosted: Sat Nov 27, 2004 4:07 pm
by Ark
That is definately not normal, but nothing GIT would be causing or able to solve. It is possible it is Winpcap or your wireless card, but the only way to know would be to swap cards.

PostPosted: Sat Nov 27, 2004 5:46 pm
by distance
Ark wrote:That is definately not normal, but nothing GIT would be causing or able to solve. It is possible it is Winpcap or your wireless card, but the only way to know would be to swap cards.



I cannot swap cards :(
I have just one... and that's for connecting to the net

PostPosted: Sun Nov 28, 2004 5:39 am
by distance
What thas this means Ark ?

Sun Nov 28 01:32:48 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.17:1459 from:80.250.15.10:80 'wrong frame type'

it's from "unforwarded log"

I have hundreds! of "wrong frame type" messages there...
10.31.1.17 is my internal WiFi network address...

PostPosted: Sun Nov 28, 2004 11:02 am
by Ark
That means you are not forwarding EthernetII frames. You choose not to forward EthernetII and it is doing what you say.

TCP and UDP packets are only used inside of IPv4 or IPv6 packets, and IPv4 or IPv6 packets are almost always only used inside of EthernetII frames on a typical LAN. Thats not to say that IPv4/IPv6 packets *have* to be used inside of EthernetII, but that is almost always the way peoples *local* networks are setup.
IPX packets on the other hand travel inside of IEEE 802.2 frames most often, which themselves travel inside of IEEE 802.3 frames.
ARP packets are typically used in EthernetII frames.

PostPosted: Sun Nov 28, 2004 1:57 pm
by distance
Ark wrote:That means you are not forwarding EthernetII frames. You choose not to forward EthernetII and it is doing what you say.

TCP and UDP packets are only used inside of IPv4 or IPv6 packets, and IPv4 or IPv6 packets are almost always only used inside of EthernetII frames on a typical LAN. Thats not to say that IPv4/IPv6 packets *have* to be used inside of EthernetII, but that is almost always the way peoples *local* networks are setup.
IPX packets on the other hand travel inside of IEEE 802.2 frames most often, which themselves travel inside of IEEE 802.3 frames.
ARP packets are typically used in EthernetII frames.



well I choose YES to forward ethernet II frames in advanced configuration of GIT ... and it was always ON

PostPosted: Sun Nov 28, 2004 2:17 pm
by Ark
That is clearly and entirely impossible. There is absolutely no way the information message can show up as "wrong frame type" unless you do not have the option set to forward that particular frame type. Clearly from your log line it says "EthernetII" so you cannot possibly have had the EthernetII frame type option checked at the time that log line was generated.

PostPosted: Mon Nov 29, 2004 2:57 am
by distance
OK :) I'm going to delete log file right now and start a GIT with Ethernet II option turned ON (checked)!

....and what do I see?!
a milinons of logs in a second!!!

---
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6d:5e:ee EthernetII IPv4 UDP to:194.108.125.242:213 from:10.31.1.17:213 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6d:5e:ee EthernetII IPv4 UDP to:194.108.125.242:213 from:10.31.1.17:213 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 UDP to:10.31.1.23:3932 from:80.32.10.184:9672 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:6881 from:193.77.245.128:3032 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:6881 from:193.77.245.128:3032 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:65:af:fe EthernetII IPv4 TCP to:193.77.245.128:3032 from:10.31.1.11:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:65:af:fe EthernetII IPv4 TCP to:193.77.245.128:3032 from:10.31.1.11:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:6881 from:193.77.245.128:3032 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:6881 from:193.77.245.128:3032 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:65:af:fe EthernetII IPv4 TCP to:193.77.245.128:3032 from:10.31.1.11:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.11:1203 from:193.95.203.172:6881 'wrong port number'
[Mon Nov 29 10:05:26 2004] network: hw:00:60:b3:6b:ac:69 EthernetII IPv4 TCP to:10.31.1.23:4554 from:207.112.14.200:4242 'wrong port number'

----


right now I'm forwarding TCP/UDP port 9999 !
and I have no idea what ports like 3023, 6881, 4242, 4554.... are doing in that LOG!?


Also those addresses "from" are totally unrecognizeable by me.
...what's going on...?

PostPosted: Mon Nov 29, 2004 3:01 am
by distance
It looks like I'm bombarding our router (10.31.x.x) with GIT and it then blocks my net connection.

When I start GIT in a few seconds my net is blocked... I cannot browse, ICQ disconnects nad cannot reconnect etc...

But when I exit GIT (or disable tunnel in GITs options) my net connection will start to work again in a few secs..

...

PostPosted: Mon Nov 29, 2004 10:29 am
by Ark
Well since you are looking at UNforwarded.log, that is a list of *all traffic* that was found on your network that was *not forwarded* because it did not match your options. If you are only forwarding port 9999, all other tcp or udp traffic on all other ports will be listed there.