Author Topic: Port Forwarding  (Read 7224 times)

Ace1

  • Posts: 108
  • Turrets: +0/-0
Port Forwarding
« on: February 17, 2007, 06:23:30 pm »
ok guys i have a problem with my ports. i have recently set up a server called the house of Ace and well i cant get the bloody ports forwarded and i have been to portforward.com and no use and i am using a bt voager 205 if that helps. so guys any help would be apprectied. TY

Ace
img]http://img515.imageshack.us/img515/6499/ace1ho5.jpg[/img]

tuple

  • Posts: 833
  • Turrets: +97/-80
Port Forwarding
« Reply #1 on: February 17, 2007, 07:10:03 pm »
This should be posted in troubleshooting or servers, or maybe even the forum for you router, NOT general discussion.

Thorn

  • Guest
Port Forwarding
« Reply #2 on: February 17, 2007, 07:59:53 pm »
Get a router...

Ace1

  • Posts: 108
  • Turrets: +0/-0
Port Forwarding
« Reply #3 on: February 17, 2007, 08:10:28 pm »
have a route and modem in one
img]http://img515.imageshack.us/img515/6499/ace1ho5.jpg[/img]

Thorn

  • Guest
Port Forwarding
« Reply #4 on: February 17, 2007, 08:39:15 pm »
a bt voyager is not a router...

Ace1

  • Posts: 108
  • Turrets: +0/-0
Port Forwarding
« Reply #5 on: February 17, 2007, 08:39:57 pm »
then wtf is it
img]http://img515.imageshack.us/img515/6499/ace1ho5.jpg[/img]

Thorn

  • Guest
Port Forwarding
« Reply #6 on: February 17, 2007, 08:58:10 pm »
A modem... The only thing that can be blocking it is your software firewall or your service provider.

Ace1

  • Posts: 108
  • Turrets: +0/-0
Port Forwarding
« Reply #7 on: February 17, 2007, 10:24:52 pm »
oh then it is the service provider wanks
img]http://img515.imageshack.us/img515/6499/ace1ho5.jpg[/img]

Diggs

  • Posts: 321
  • Turrets: +5/-11
Port Forwarding
« Reply #8 on: February 18, 2007, 04:02:24 pm »
Actually they do say it is a router and give the details for port forwarding here-

http://www.portforward.com/english/routers/port_forwarding/BT/Voyager205/SlingBox.htm

It may not be what you want as I did not read the whole thing.

You may also want to forward a small block of ports, say 30720-30730 (I think 30720 is Trem's default port).  For some reason I have found this helps on Quake servers that refuse to run on one open port.  If all else fails, DMZ the whole machine for testing, but don't leave it there.

Diggs
続けてゲーム

Diggs

  • Posts: 321
  • Turrets: +5/-11
Port Forwarding
« Reply #9 on: February 18, 2007, 11:59:41 pm »
Your router admin screen should look like this-



Hit the drop downbox and click on DMZ.  Fill in the IP of your server and click apply.  There -  your server is outside the router.  No forwarding required.  This is not a good security risk.  As soon as you verify it works this way, change it back to behind the router.  Drop the box back to server and fill in the ports for Tremulous.

BTW- If you have server and client together behind the router and they are both using the same port address, occasionally weird things will happen due to a port conflict.  If you have a port conflict, just start your server on another port like 30730, instead of 30720.


Diggs
続けてゲーム

FooBar

  • Posts: 94
  • Turrets: +9/-1
    • http://avalanche.server.googlepages.com
Port Forwarding
« Reply #10 on: February 19, 2007, 05:57:34 am »
Diggs is right: if your server and the computer you usually play on are both behind the router, you absolutely MUST set the server to use a different port from the default.  If you set up port forwarding for the Tremulous default port, you won't be able to see any servers on the master server list.

I mean, set the server to use some totally different port like 32000, and do your port forwarding for that port.

Here's why:

Let's say you have a gaming machine with local IP address 192.168.1.10, and your server has local IP address 192.168.1.20.  Let's say your server is set to use the default Tremulous port, 30720.

Port forwarding makes any signals coming from the Internet on port 30720 get AUTOMATICALLY sent to your SERVER at 192.168.1.20.  Why is this a problem? Well, when your gaming computer talks to the master server (and most Tremulous servers), it sends signals out on port 30720 and the master server sends signals BACK on port 30720.  The signals you send out aren't affected, but the signals coming BACK, which are meant for your gaming computer, are routed by the Port Forwarding to your server because they're on port 30720!

So your gaming computer can send signals on port 30720, but it can't receive any signals.  Only your server can receive signals on port 30720.  As a result, your gaming computer can try to talk to a Tremulous server, but it will never get a reply... because the replies get misdirected to YOUR server because of your port forwarding!

The result?  Your master server list will be almost empty, except for a few servers that use non-standard ports.

The solution?  Use a non-standard port on your server, preferably one that no one else uses.

Remember this too: whatever port you use for your server, you will NEVER see your server on the master server list if you have port forwarding working.  The reason is basically the same as above.  In order for you to talk to your own server, you will need to manually make a "Favorites" entry in Tremulous using the local IP address and port of your server; in the above example, it would be 192.168.1.20:32000.

Ace1

  • Posts: 108
  • Turrets: +0/-0
Port Forwarding
« Reply #11 on: February 19, 2007, 01:16:28 pm »
Ok guys i have got to the part were the drop down menu appears Ok

After this point i cant get no futher when the advanced tap drops down i cant do anything after that. When the drop down menu appears i click on ip routing and nothing happens, and if i click on any of the others nothing happens. I have been at this point a thousand times and i cant get by it :(

would you recomend buying a new modem and router????
img]http://img515.imageshack.us/img515/6499/ace1ho5.jpg[/img]

next_ghost

  • Posts: 892
  • Turrets: +3/-6
Port Forwarding
« Reply #12 on: February 19, 2007, 04:38:02 pm »
Quote from: "FooBar"
Diggs is right: if your server and the computer you usually play on are both behind the router, you absolutely MUST set the server to use a different port from the default.  If you set up port forwarding for the Tremulous default port, you won't be able to see any servers on the master server list.

I mean, set the server to use some totally different port like 32000, and do your port forwarding for that port.

Here's why:

Let's say you have a gaming machine with local IP address 192.168.1.10, and your server has local IP address 192.168.1.20.  Let's say your server is set to use the default Tremulous port, 30720.

Port forwarding makes any signals coming from the Internet on port 30720 get AUTOMATICALLY sent to your SERVER at 192.168.1.20.  Why is this a problem? Well, when your gaming computer talks to the master server (and most Tremulous servers), it sends signals out on port 30720 and the master server sends signals BACK on port 30720.  The signals you send out aren't affected, but the signals coming BACK, which are meant for your gaming computer, are routed by the Port Forwarding to your server because they're on port 30720!


If that happens to you, you should consider returning your router to the manufacturer because it's obviously broken. NAT doesn't care about source port of packets leaving your network unless it's told to do so by port forwarding rule. It'll change the source port to whatever port is available at the moment and when a reply comes back to the same port, it'll send it to the right machine inside your network. It'll never use port ranges taken by active port forwarding rules.
If my answer to your problem doesn't seem helpful, it means I won't help you until you show some effort to fix your problem yourself!
1.2.0 release's been delayed for 5:48:00 already because of stupid questions.