Multiple servers under one box hosted localy; only one shows

[Psychcf]

I was setting up a new TSA CTF server on my current server, and I still have the old DM set to the port 26000. So, I set the new one to port 26001, and it wasn't showing up on the server list. Huh? I go over to another server and ask someone if he sees both of them, he says he does. I don't think it's my router, because when I go to the console and connect to the CTF server, it works fine, it's not showing up localy though.

This isn't a big deal, but it still is a "bug" mabie.

[esteel]

I know 'local' servers are only found if they are on port 26000 but when others see your servers in the server list those are registered on the master server and your nexuiz also gets that list and tries to contact your server with its public IP.. And this seems to not work properly so maybe your routing is not totally correct..
And then nexuiz tries to find server on the local network on port 26000 and find that one..

[tChr]

wtf esteel.. I know how this works but I still have problems understanding what you write..

anyhow
The server browser shows all servers that are on a local network and answering on port 26000, it also shows all servers that are public and reports themselves to the master servers.
If you have a server running on another port than 26000 and it reports itself to the master server, it will show up in the lists, you will be able to connect to it if your setup in the router is correct, however, performance wise, I'd still connect to the local ip.

iirc you will find all local servers running on 26000 no matter if they are sv_public or not

[esteel]

Well it was late when i wrote that post but in general i hope i wrote the same as you tChr

However as he does not find the second server but can only see the first server running on port 26000 in the server browser i think he can't reach 'his server' by its public IP so something with the routing in his network must be wrong.

[divVerent]

This is quite common behind NAT, for example when using Linux on the router, it is disabled by default.

If you have the public IP 224.17.23.1 a port forwarding from udp/26000 to your Nexuiz server 192.168.0.42 and are in the LAN, if you try to access 224.17.23.1 from your LAN, it would first go to the router and then the router would need to forward the packet out on the SAME interface. Linux prevents that and regards this as an IP spoofing attempt.

To enable that type of access, you can disable the "rp_filter".

[Psychcf]

esteel: errr I wanted to get a new router anyway...

[esteel]

No idea if a new router will fix this.. what divVerent suggests souds plausible and i doubt many router allow you to change this

[divVerent]

Yes, what I wanted to say: this effect is quite normal, live with it and use the connect command manually, as in "connect 192.168.0.3:26002" on the console.

Another option could be running your own dpmaster in your LAN, and setting it as additional master server in your game.

The next solution would be using interface aliases to make one computer handle multiple IP addresses in your LAN, and putting them in net_address of each instance. Then all server instances will be able to respond to the broadcast query.

[Psychcf]

I'm way too lazy to do any of that, plus port forwarding is a bit screwy, and it's pretty old, and it's the one they give you when you sign up for your ISP, so I need a new one anyway.