Server Help

Jason · Posted: Mon Jun 20, 2005 2:59 am Post subject:

I'm not sure if it's even necessary for me to be doing this, but I'm trying to set up port forwarding even though I'm just running a client. I keep running into lag issues (my tinfo is nuts), and port forwarding fixed some problems in other areas (namely filesharing). So then, I thought I'd give it a try with SS as well.

I just have two questions. Do I need to use the server port? (The one that shows up when you right click on a zone in the zone list.) And do I use UDP or TCP or both?

Mine GO BOOM · Posted: Mon Jun 20, 2005 3:21 am Post subject:

Port forwarding will do nothing for your client. The way Continuum and other clients work, is that they begin talking with the client. Since they send out the first packet, your NAT device (router in your case) notices this, and remembers this connection. So all future data that comes in with similar ports/ips will be forwarded to your system. Its like a temporary port forwarding.

If you are having problems with this, as you feel you are, forwarding the ports won't do much. Clients choose a random local port for their connection. Try connecting to a zone, and typing netstat -a -n -p UDP in a command prompt. Then quit and re-enter the zone or a different one and type the command again. The only way to forward the local ports would be to forward all ports, which would kill the idea of being behind NAT in the first place.

If NAT would forget your connection state, it usually means that your NAT device ran out of memory and it had to remove a state from its table. If you are running a program like Bit Torrent or Kazaa which connects to many people at once, this can cause problems with most home routers, and you'll either need to buy an expensive router or make one running Linux/BSD on a spare computer. Just remember, as soon as you send out a new packet to the zone (ie: ship position, chat message, etc), the NAT device will renew the state in its table, or make a new one. So if it causes problems, it will be for split seconds only.

If your tinfo is off, thats usually a clock problem with your computer. Azureus, a Bit Torrent client, has been a known problem for this. Other things can be hardware related, but usually software related. Try posting a *tinfo of yourself here some time, and I can suggest how big of a problem an unsynced clock will cause you (usually almost nothing, unless you are gaining/losing hours per day on your system clock).

Jason · Posted: Mon Jun 20, 2005 3:30 am Post subject:

You hit the nail on the head, MGB. My roommate and I share a 3.0Mbps/768Kbps DSL connection. The greedy bastard seemingly always has torrents going, and while he's not killing our bandwidth, I figured that was the culprit. I've told him countless times to save the downloading for overnight, but he won't listen.

Just how much do you think purchasing a router with a larger NAT table would help me out? I was browsing through the broadbandreports.com forums, and apparently there's a wireless Linksys model that you can get hacked firmware for, allowing for something like 8k entries in the table.

Mine GO BOOM · Posted: Mon Jun 20, 2005 12:52 pm Post subject:

Jason · Posted: Wed Jun 22, 2005 4:08 pm Post subject:

Marvelous! Thanks for all the info. I've ordered that router, and it should be here by the end of the week.