Does GIT work with Class B subnet aswell?

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

Does GIT work with Class B subnet aswell?

Postby Hazza » Tue Jul 31, 2007 8:28 pm

Hi guys.

Firstly Ark, top work! Fantastic program.

Quick question. I know it is recommended to have the two private networks, that are being tunnelled, share the same class C subnet (ie 192.168.1.x 255.255.255.0), but does GIT still work correctly when a class B subnet is used (ie. 192.168.x.x 255.255.0.0)?

Cheers.
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm

Postby Ark » Tue Jul 31, 2007 10:26 pm

GIT does not care about the subnet or netmask, etc. It just finds packets on the network, tunnels them over to the other GIT, and rebroadcasts the packet onto the opposite network.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Hazza » Wed Aug 01, 2007 4:35 am

Excellent. So why does everything I have read so far say that the computers on both LAN's need to share the same subnet and mask (but not conflict)?

ie. all advice is to have one LAN from 192.168.1.1 to say 192.168.1.10 and the LAN on the other side of the tunnel to have say 192.168.1.11 to 192.168.1.20 with the same mask?
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm

Postby Ark » Wed Aug 01, 2007 8:18 am

It really depends on the application you are using with GIT. Many send broadcast packets to the network and if the computers on the other side of GIT are on a different subnet, they will see but ignore the broadcast packet that GIT re-sends onto that network.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Hazza » Thu Aug 02, 2007 5:41 am

I understand. Thankyou for the explanation.

One other thing if I may Ark. We have successfully got GIT configured to play GRAW2 (Ghost Recon Advanced Warfighter 2) and works perfectly. But at random times when we are not playing games, ie during the day when our connections have been idleing for a while GIT local stops talking to GIT remote even though nothing has been changed (traffic is logged as forwarding to each other but neither see incomfing). It seems hard to get them talking again, but if we change port from 213 to 214 for example it comes back working again straight away. Any ideas?
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm

Postby Ark » Thu Aug 02, 2007 7:22 am

I'd guess you have a firewall or some router between GIT and the outside world which may time out the UDP opening for mapping the incoming packets to the computer running GIT. Some cheap routers are really bad with keeping connections open at times.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby Hazza » Thu Aug 02, 2007 10:47 pm

Yep that is definately possible. But the problem is not that the connection drops when idle, it is that if this does occur, and we come back that night and everything pings fine to the outside world, the GIT tunnel does not seem to recover even after restarting routers etc.

Usually we need to change the port and/or protocol the GIT tunnel is using to get communication back. The GIT logging on forwarded packets is fine from both ends, but both ends do not get the corresponding incoming packets. After we fiddle with GIT ports/protocols (with no router/firewall changes) it comes back up again. I am not saying at all that it is GIT causing the problem but router/firewall is not touched between the not working and the working. Wondering where to try and troubleshoot.

Thankyou for all your responses.
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm

Postby Hazza » Thu Aug 16, 2007 7:33 am

Thought I would post back here with an update. I got my friend to reset his router to factory defaults and redo his settings. Since then GIT has been flawless.

THANKYOU ARK!!! Once again thankyou for a TOP PROGRAM. You have allowed us to experience gaming bliss with your software. :D
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm

Re: Does GIT work with Class B subnet aswell?

Postby DeVastoR_DVR » Sat Nov 03, 2007 9:48 am

Hazza wrote:Hi guys.

Firstly Ark, top work! Fantastic program.

Quick question. I know it is recommended to have the two private networks, that are being tunnelled, share the same class C subnet (ie 192.168.1.x 255.255.255.0), but does GIT still work correctly when a class B subnet is used (ie. 192.168.x.x 255.255.0.0)?

Cheers.


well 192.168.x.x IP are reserved for class C so they cannot be used as class B (or shouldn't be able to) even with subnet of 255.255.0.0

If you want a class B, I would suggest using 172.16.x.x IPs which are class B, or 10.x.x.x for class A
DeVastoR_DVR
 
Posts: 5
Joined: Sat Nov 03, 2007 9:43 am

Postby Ark » Sat Nov 03, 2007 9:56 am

CIDR has kind of obsoleted the model of ranges of IPs being pre-determinable as class A/B/C, so you can use 192.168.0.0-192.168.255.255 as a big class B if you want, it isn't going to hurt anything, and it isn't even routable over the internet anyway, so nobody will know.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby DeVastoR_DVR » Sat Nov 03, 2007 12:38 pm

you probably have a point there, just what i learned from network+ and cisco books
DeVastoR_DVR
 
Posts: 5
Joined: Sat Nov 03, 2007 9:43 am

Postby Hazza » Mon Nov 12, 2007 6:09 am

Yeah Ark is right. You can use the 192 space for whatever you like really. There may be some software out there that doesn't like it, but 99 percent of it wouldn't care.
Hazza
 
Posts: 7
Joined: Tue Jul 31, 2007 8:20 pm


Return to GIT

Who is online

Users browsing this forum: No registered users and 12 guests

cron