why not forward all ports and sockets to encompass all game?

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

why not forward all ports and sockets to encompass all game?

Postby poseyjmac » Fri Oct 29, 2004 8:38 pm

ive been using GIT for a while, and ive always used ethereal or the GIT built in logger to find out ports for each game. but im wondering, whats a good reason not to just forward all ports and sockets?

say im connecting 2 LANS through GIT and we want to try several games, will we see any higher latency/pingtimes because we opened up all the ports and sockets? this has been nagging me for a while, whats the truth on this matter? thx
poseyjmac
 
Posts: 42
Joined: Mon Mar 29, 2004 11:33 pm

Postby Ark » Fri Oct 29, 2004 9:57 pm

Well for one, you dont want to forward the GIT ports, or you create an infinite loop of forwarding a packet that is really a packet inside a packet being forwarded.
Yes, you will easily waste bandwidth, especially if you forward netbios ports such as 137-139 or 445 or other ports lots of traffic may appear on.
You don't want to forward traffic your ICQ or AIM is using, since that will just waste bandwidth, even if you are chatting on it sometimes.
Also, it may be a security risk to allow some ports to be forwarded, since anybody can inject packets into your local network, bypassing any external firewall or NAT, if they try hard enough. GIT will reject packets to any port you aren't forwarding, so if you set GIT up to only forward for a game, that game's ports is all that is exposed to the outside world if you are normally firewalled or behind NAT.
Ark
Site Admin
 
Posts: 2108
Joined: Sat Sep 13, 2003 4:21 pm

Postby poseyjmac » Fri Oct 29, 2004 11:22 pm

ahh i see. thanks
poseyjmac
 
Posts: 42
Joined: Mon Mar 29, 2004 11:33 pm


Return to GIT

Who is online

Users browsing this forum: No registered users and 22 guests

cron