BIG PROBLEM WITH DEDICATED SERVER ON NAT ;-(((((((((((

[mitar]

I host server, it start on local ip with port I set...
but in server browser (internet) in game there is another port , and when router restart there is another port ;/
I have "stand IP"
I try this  +set net_qport 12345 (this is Setting for NAT)
but it not help ;(
(SORRY FOR MY ENGLISH)

[darklurker]

Mitar,

Was it a typo when you wrote "+set net_qport"???  Isn't it supposed to be "+set net_port" -without the "q"?

Anyway, I'm behind a NAT firewall myself, and it's working OK for me on port 30720.  Just make sure your firewall will allow outbound traffic on port 30710 - which I think is what tremded uses to send heartbeats to the masterserver.

good luck,
DarkLurker (aka David)

[SysmiX]

I have the same problem, my server don't show in the ingame list. On an external server browser (XQF), my server show but is unresponsive. The server browser can't get any info from it. The weird thing is that using the "connect" command, my friends can connect.

I'm using the "+set dedicated 2" parameter, and on the server console i get:

Code: [Select]

Resolving master.tremulous.net
master.tremulous.net resolved to 72.36.226.187:30710
Sending heartbeat to master.tremulous.net
Hitch warning: 11182 msec frame time
Sending heartbeat to master.tremulous.net
...
...

The server is running on the 30720 port (confirmed) but in the XQF server browser, the reported server port is 60165 or some other random port close to that. I think that every heartbeat add a new entry in the master list with a different random port and the old ones get deleted after some time. Right now, there is three entries of my server in the list, all unresponsive.

It's running on linux btw.

I have tried the "+set net_port 30720" with the same results. Can I specify the address I want the server to report to the master even if its not the host ip? Maybe this problem is caused by some NAT craziness of my router. I'm running out of ideas, any help will be appreciated.

[Odin]

Tell us the nature of your local area network. What kind of connection, modem, router, etc.

[SysmiX]

It's an adsl connection. My modem is a siemens speedstream 4200 working as router with the DMZ set to my machine's LAN ip. The connection is well tested and working ok. Other local services can be accessed from the internet.

[next_ghost]

You need to specify the exact port on the modem, otherwise NAT daemon might grab the first free port it finds for outgoing traffic.

[Odin]

Also, make sure your router is making the ISP connections with PPPOE, and not using DHCP mode to communicate with the modem. Call your ISP and ask them how to get your modem running in bridge mode, since most modems come defaulted to work by connection with a single computer, thus the modem's onboard OS is doing all the work. This can have a drastic effect on NAT networks, and I used to have this problem until I switched my modem into "bridged" mode and made the router do the ISP connection through the modem with PPPOE instead.

If you can access both your modem and your router with a web interface, check if your router is set in PPPOE mode. If so, this problem shouldn't be occurring.

[SysmiX]

I don't think I can specify the port that NAT use on the outgoing packets. And I just got this modem because of the router capabilities as I have 3 computers using this connection and none stays 24h online to be the gateway. The modem have two kinds of NAT, the simpler allows only one internal machine to access the inet (this one works ok but don't fit my needs), and the second, NAPT, do this port number changing madness and cause the trouble. But the server works ok, it just show up with the wrong port in the master list. I guess I'll have to live with that   .

The only way I can see to solve that is to have an way to send the address of my server to the master list in the data of the network packet, and not using the source address of the connection, if there is no such thing already, it's probably not going to be done, as it's probably an standard protocol (from the quake engine i guess).

Thanks to you guys for the help, to bad it had no solution.

[next_ghost]

That's the first NAT capable modem which doesn't support port forwarding I've ever heard of.

[SysmiX]

It support port forwarding, the server can be reached from the Internet, the problem is just sending the right address to the master list. I don't know the protocol, but I'm guessing the master server uses the source address of the heartbeat as the server address. And when my server send the heartbeat with the source address set to 192.168.254.1:30720, the router change the ip to my WAN ip, but it also change the port for some reason and that's the problem.

[next_ghost]

It support port forwarding, the server can be reached from the Internet, the problem is just sending the right address to the master list. I don't know the protocol, but I'm guessing the master server uses the source address of the heartbeat as the server address. And when my server send the heartbeat with the source address set to 192.168.254.1:30720, the router change the ip to my WAN ip, but it also change the port for some reason and that's the problem.

Why haven't you set up a simple port forwarding rule then?!
forward 30720 => your_LAN_ip:30720
That's ALL you have to do to keep the same port for all outbound Tremulous server traffic.

[SysmiX]

Oh, only now I see you was talking about *outgoing* traffic, it worked!! Thanks very much. I had tried that before but with a port range and that don't helped.