PK 1.64 linux LAN sever doesn't show up in ingame browser

[Fisch.666]

Hi!

I have a problem with my 1.64 linux lan server (OS is debian sarge). I can't see the server in the ingame browser nor in tools like hlsw, ase etc. But when i enter the ip to the "Enter IP" box and click on "join" i can connect/play on the server without a problem. Firewall/netfilter is deactivated so ther should be no problems with blocked ports. (All other gameserver like BF1942, HL² etc running without a problem)
When the server is running, netstats -nlut looks like this:

udp 0 0 192.168.0.3:3578 0.0.0.0:*
udp 0 0 192.168.0.3:3455 0.0.0.0:*

so the painkiller ports are bound to the right ip.


This is my commandline to start the server:

./pkserver +dedicated +interface 192.168.0.3

I use the standard config.ini, but changed this two lines:

Cfg.DedicatedServer = false
to
Cfg.DedicatedServer = true

and

Cfg.PublicServer = false
to
Cfg.PublicServer = true


Any ideas how i can fix that problem? Thanks in advance for your replys!!!

For all german users, i've posted this already in the german www.inpainkiller.de forum:
http://forum.ingame.de/painkiller/showthread.php?s=&threadid=1110&perpage=20&pagenumber=2

[kalme]

I have a problem with my 1.64 linux lan server (OS is debian sarge). I can't see the server in the ingame browser nor in tools like hlsw, ase etc. But when i enter the ip to the "Enter IP" box and click on "join" i can connect/play on the server without a problem. Firewall/netfilter is deactivated so ther should be no problems with blocked ports. (All other gameserver like BF1942, HL² etc running without a problem)
When the server is running, netstats -nlut looks like this:

udp 0 0 192.168.0.3:3578 0.0.0.0:*
udp 0 0 192.168.0.3:3455 0.0.0.0:*

so the painkiller ports are bound to the right ip.

This is my commandline to start the server:

./pkserver +dedicated +interface 192.168.0.3


Ok...
in your German post you say that your server has two NICs, one for your LAN and one for your internet connection.


192.168.1.1 (LAN IP)
192.168.0.2 (internet-"side" IP, connected to a router)
Now first of all, why are you trying to bind your server to a non-existing interface (192.168.0.3)? Second, your local network is 192.168.1.0. When you bind your server to an ip in a different subnet (192.168.0.0), why do you expect it to show up in the in-games LAN-browser (that's what you want according to your German post)?

One thing I also came across is that you may indeed face problems with the clients you wouldn't expect. For example, if you're using an VPN client like OpenVPN that works with a virtual network interface on your LAN-clients, you may end up with Painkiller binding to that virtual network interface. That way you also can't see your LAN server, although client and server are physically/technically connected to the same network. This happened to me before and it's not the servers fault.


Cfg.PublicServer = false
to
Cfg.PublicServer = true
If you don't want your server to show up in public, you don't need to set this option to true. With this set to false, your server still will show up in your client's LAN-browser (if bound to the right interface). "Rid" in that German forum gave you some bad advice on this or at least was very vague about it.

Another thing. In your German thread you say that you can't understand why your server only shows up in server browsers like ASE when you start it with a working internet connection. Well, these server browsers connect to master servers that trace all available servers on the internet. You can't use them with local (LAN) servers. So for your server to show up in ASE he needs to connect to the masterserver first, thus the need for an internet connection.

***

I suggest the following: if you want to use your server in your LAN only (and want it to show up in the in-game LAN-browser), then set Cfg.PublicServer = false and use the following command line to start it:

./pkserver +dedicated +interface 192.168.1.1

If you want to use it as public server, go with Cfg.PublicServer = true and use

./pkserver +dedicated +interface 192.168.0.2

Your server then will show up in ASE and other browsers, and it should show up in the internet in-game browser too (for some reason, this sometimes takes up to a few minutes for me). It won't show up in the LAN-browser though (due to the different networks), but you know that already.

Hope that helps...

[kalme]

And another thing I forgot. You also asked about running PK++ on your server, and you also got some not-so-accurate information about this on that forum. There's a description of how to set up things in the PK++ documentation. Also, I suggest you head over to pkeuro.com, they have some information about this in their forum. And there's an (well-commented) update shell script for linux that saves you the trouble from doing that manually all the time. Go and get it here:

http://www.pkeuro.com/comments.php?blogid=2&eid=122

[Fisch.666]

Hi!

First, many thanks for your reply!!!!



in your German post you say that your server has two NICs, one for your LAN and one for your internet connection.


Now first of all, why are you trying to bind your server to a non-existing interface (192.168.0.3)?


I have only one NIC wit the IP 192.168.0.3 at my server, so the +interfaces 192.168.0.3 schould be ok. I'am the User Fisch.666 in this thread, not the threadstarter wich has 2 NICS.



If you don't want your server to show up in public, you don't need to set this option to true. With this set to false, your server still will show up in your client's LAN-browser (if bound to the right interface). "Rid" in that German forum gave you some bad advice on this or at least was very vague about it.


Ok, i will try this again. Thanks for this hint!!!!



Another thing. In your German thread you say that you can't understand why your server only shows up in server browsers like ASE when you start it with a working internet connection. Well, these server browsers connect to master servers that trace all available servers on the internet. You can't use them with local (LAN) servers. So for your server to show up in ASE he needs to connect to the masterserver first, thus the need for an internet connection.


HLSW and ASE can search for LAN Servers which have no connection to the master browser. All other Servers like BF1942, HL, HL², Call of Duty wich are installed at my server are working without a internet connection so i thought painkiller should work too...

[kalme]

I have only one NIC wit the IP 192.168.0.3 at my server, so the +interfaces 192.168.0.3 schould be ok. I'am the User Fisch.666 in this thread, not the threadstarter wich has 2 NICS.
Ooooops... guess I could have figured that out comparing the nicknames myself... sorry.


ASE can search for LAN Servers which have no connection to the master browser
Maybe I should take a look at ASE again, seems like I'm not up-to-date feature-wise anymore. Sorry again.


All other Servers like BF1942, HL, HL², Call of Duty wich are installed at my server are working without a internet connection so i thought painkiller should work too...
I did a short test here too. When I start my Painkiller dedicated server with "Cfg.PublicServer = true", it also shows up in the LAN-tab. But if I block the servers internet connection, I've got the same effect -- no server visible in the LAN-browser. I think the reason for that is that my server didn't bind to the LAN network interface then, but to 127.0.0.1, which is kind of weird...

[Fisch.666]

Hi!

Thanks again for your reply!



I did a short test here too. When I start my Painkiller dedicated server with "Cfg.PublicServer = true", it also shows up in the LAN-tab. But if I block the servers internet connection, I've got the same effect -- no server visible in the LAN-browser. I think the reason for that is that my server didn't bind to the LAN network interface then, but to 127.0.0.1, which is kind of weird...

Strange, should we report this to PCF/Dreamcatcher? Maybe they can fix this in the next version.