I am running a server behind a firewall, but it does not show up in the public list. I have had people connect from the outside; so I know the server itself does work.

I am running the server on port 27000, if that matters..

Any ideas?

-Jer

Is the server set to public? Try

Code: Select all

sv_public 1
heartbeat

in the server console (that will make the server public and force it to notify the master server immediately).

KadaverJack wrote:Is the server set to public? Try

Code: Select all

sv_public 1
heartbeat

in the server console (that will make the server public and force it to notify the master server immediately).

Yah.. have "sv_public 1" set; still doesn't seem to work.. How long does it take to show up? Also, is this link a reliable way to see if it is listed?

http://dpmaster.deathmask.net/?game=nexuiz&sort=players

Lunacy wrote:How long does it take to show up?

After "heartbeat" it should only take a few seconds.

Also, is this link a reliable way to see if it is listed?

Yes, I think it's updated in realtime, but i'm not 100% shure...

But i also don't see your server in the list (there are only 2 servers on port 27000, there's also no unconnectable server on that port). Does you r firewall have a way to see which packets were blocked? Check if it's blocking any connections to ghdigital.com, dpmaster.deathmask.net or excalibur.nvg.ntnu.no (port 27950/UDP).

Edit: now there's a third server on port 27000, is that yours? http://planetnexuiz.de/qstat/popup.rb?74.0.49.66:27000

KadaverJack wrote:

Lunacy wrote:How long does it take to show up?

After "heartbeat" it should only take a few seconds.

Also, is this link a reliable way to see if it is listed?

Yes, I think it's updated in realtime, but i'm not 100% shure...

But i also don't see your server in the list (there are only 2 servers on port 27000, there's also no unconnectable server on that port). Does you r firewall have a way to see which packets were blocked? Check if it's blocking any connections to ghdigital.com, dpmaster.deathmask.net or excalibur.nvg.ntnu.no (port 27950/UDP).

Thanks for the information; it is in fact updated in real time.. I figured it out..

The deal is this, when my firewall was doing NAT it was changing the source port of the packet being sent from the server out.. I changed the rule such that it didn't do that, and it worked..

It is an OpenBSD system running pfctl, and the nat rule that worked looks like this:

nat on $ext_if from $dmz_if:network to 72.232.48.140 -> ($ext_if) static-port

The "static-port" is the important part of this..

-Lunacy

man oh man do I hate nat. Because of this I looooove UPnP.

[TSA] Psychiccyberfreak wrote:man oh man do I hate nat. Because of this I looooove UPnP.

NAT has ups and downs Woot.. My server is Boston TDM in the server list, FYI

-Lun

Nice, hope it receives enough players