Hi.
I'm just starting to run a Nexuiz server and there's a few questions mainly about correct announcement of it in the list.
The server is placed in home network behind NAT router with two internet uplinks which means it can be available via three IP-addresses - one private and two public.
Now I see only two "instances" of my server in the list while joining - a private and a public via main uplink. I believe, it is available via backup link too, but it isn't get announced because of that link is rarely used.

1. Should I worry about my private IP appearing in the global list?
2. How can I add second public IP to the list? Maybe manually?
3. Is there any way to tell clients where to connect (in config.cfg or so)?

Thanks for any attention to this topic

I just can't read this

Tamagoch wrote:Hi.
I'm just starting to run a Nexuiz server and there's a few questions mainly about correct announcement of it in the list.
The server is placed in home network behind NAT router with two internet uplinks which means it can be available via three IP-addresses - one private and two public.
Now I see only two "instances" of my server in the list while joining - a private and a public via main uplink. I believe, it is available via backup link too, but it isn't get announced because of that link is rarely used.

1. Should I worry about my private IP appearing in the global list?
2. How can I add second public IP to the list? Maybe manually?
3. Is there any way to tell clients where to connect (in config.cfg or so)?

Thanks for any attention to this topic

Fullquote; next time don't use the color tag. Thanks.

1. The private IP does not appear in the global list, what you see is the client sending a broadcast to find LAN servers - under the local IP - and at the same time asking the master server for a list - which includes the public IP.
2. No, you can't add a second public IP. The server does not send its IP to the master server as it can't know its public IP from behind NAT - it just sends a packet there and the master uses the sender address as server IP.
3. You can use "connect 1.2.3.4" from the console or from the command line:

Code: Select all

./nexuiz-glx +"connect 1.2.3.4"

divVerent wrote:Fullquote; next time don't use the color tag. Thanks.

I forgot about main skin color, sorry...

divVerent wrote:3. You can use "connect 1.2.3.4" from the console or from the command line:

Yes, now I remember - it's the same commands as in Quake So many time has passed...
Thanks for all your answers, now I know what to do.

BTW, is there any requirements for server hardware?
I don't want to split resources with my other game server, but there's only old Celeron 1.3 I've got now without heavy load.

Tamagoch wrote:BTW, is there any requirements for server hardware?
I don't want to split resources with my other game server, but there's only old Celeron 1.3 I've got now without heavy load.

should be enough.. the one i ran on my duron 1,6 used around 5% cpu..

esteel wrote:should be enough.. the one i ran on my duron 1,6 used around 5% cpu..

yes, it's really enough - I've made some frags recently
maybe the usage of RAM is more important resource - ~130 Megs per server I suppose
so I won't be able to run another one, gotta find more DIMMs

You can reduce the memory usage by about 60MB, if you delete the models/ folder from data*.pk3 with 'zip -d data*.pk3 models/*' or another zip program.

KadaverJack wrote:You can reduce the memory usage by about 60MB, if you delete the models/ folder from data*.pk3 with 'zip -d data*.pk3 models/*' or another zip program.

Great! I'll do it. If these files are needed for clients only I shouldn't worry 'bout them