Is the only incoming port needed for a Nexuiz server 26000 udp? I have recently started using IPCop as my gateway/firewall and I have port 26000 UDP fwd'ing to my server and it is not showing up on the list of available servers. My Server has more responsibilities than just Nexuiz and other services that required fwd'd ports are working just fine. Any ideas?

Also is it normal when the server starts to see "0.0.0.0:26000" in the command prompt box? It may be that Nexuiz cannot figure out what my external IP is. Any ideas?

Thanks in advance,
7im

There is a variable that tells your server to show up on the public list. I don't know it offhand (sv_public?).

7echno7im: This is completely off topic, but someone had said that your server was a minstagib only server. I know in the past you had problems with certain maps changing the gamemode to that, but wasn't sure if you wanted that or not. Just informing you if you haven't been on your server lately that there are still maps on there changing the gamemode. If this is how you want it, then no worries.

7echno7im wrote:Is the only incoming port needed for a Nexuiz server 26000 udp?

Yes (unless you changed the default port, of course).
But as Dokujisan already mentioned: sv_public must be 1 (iirc it's off by default).

Also is it normal when the server starts to see "0.0.0.0:26000" in the command prompt box?

Yes, 0.0.0.0 means: listen for incomming connections on all network devices.

You could go to IRC and ask someone to try to connect to your public IP directly just to test the port forwarding.

Or post the IP here.

Or try http://planetnexuiz.de/qstat/popup.rb? ip>

Yeah I am aware of the public posting option. As I said before i replaced my older gateway with a new Linux box I built with IPCop, I had Nexuiz running just fine and have not changed the config file at all. I just didn't have m forwarding rules to compare to. I will investigate IPCop and se what it is doing.

Mr. C. I am ware of it getting stuck in that game mode, I have a different post in the bugs, no one seems to have a good solution yet.

see my post here http://alientrap.org/forum/viewtopic.php?t=1914

I use ipcop and host a server every now and then, never had a issue with ipcop. do doublecheck that you forwarded the udp port. i hit GRE by mysstake or simply forgot it at TCP a few times..

here is my IPCop Entry

UDP DEFAULT IP : 26000 => 10.1.1.50 : 26000 Nexuiz UDP

it matches the IP on my server


here is the config file entry:

port 26000 // the port used by the server
sv_public 1 // 0 if the server should not be on the public servers list


I am not sure what is wrong. It worked fine with my old firewall.

Is that the only entry you have in IPCop that even refers to the Nexuiz server? Did you have to set external access too on the firewall tab? I thought about that, but that should only be fore the IPCop box itself. All of my other ports are forwarding fine, even ports to the same server but different services.

the communication with the master server is on another port.. wtf was it udp 27500 or smnth. so if thats closed you will not be listed in public list, the game itselv funs on 26000 by default.

tChr wrote:the communication with the master server is on another port.. wtf was it udp 27500 or smnth. so if thats closed you will not be listed in public list, the game itselv funs on 26000 by default.

Only the master server itself runs on port 27950, the gameserver always uses port 26000 (or whatever port is given).
(the master server actually takes the port number from the source port of the heartbeat package)

so just to recap, only port 26000 UDP is needed to host a server (with default server.cfg values), no other port is used to announce itself?

To cap up, your server need to be able to send message to master server if you want it publick, you outboudn 27950 udp must be open. inbound udp 26000 should be ebough,.

Outbound everything must be open, or others can't connect to your server.

thanks all for the info.