How to up an server public and on.

[Debci]

I need a little howto  because i cant up the sevrer to public, i modified the hosts files in my ubuntu 9.04, and i added an host to no-ip.
my hosts file are this:
192.168.2.100        mynoip.no-ip.biz
localhost                  mynoip.no-ip.biz

I opened the port in TCP mode, i started the sevrer, i refreshed the ip on dns and nothing...

Please help-me.

[ThomPhoenix]

Is the server itself ready? (the cli command is "ready").

[Debci]

yes, maps loaded spawn and ready

regards

[Pizik]

PlaneShift uses UDP so opening your TCP ports will not help. You need bidirectional UDP port open.

[Debci]

ok, but when i connect with my no-ip, in my pc has no-ip = localhost, Data/servers.xml and in this to my no-ip, and the game not connect to the server.

regards

[Sen]

As a detail, your hosts file should better look like
192.168.2.100        mynoip.no-ip.biz
127.0.0.1        localhost

You can enter something like this in your servers.xml of your planeshift client:
<serverlist>
<server name="Fragnetics" ip="laanx.fragnetics.com" port="7777" />
<server name="ezpcusa" ip="planeshift.ezpcusa.com" port="7777" />
<server name="MyOwnServer" ip="192.168.2.100" port="13331" />
</serverlist>

By the way, is your own server marked as "Failed" or is something else the problem?

Sen

[Lanarel]

Can you connect to your server from a client on the same machine (with as server ip 127.0.0.1 in servers.xml)? If it is that you can connect but others cannot, you may also have to forward the external IP to you local up (the 192 one).

[Debci]

yes i can connect to my sevrer with localhost.

regards

[Vornne]

I use a DNS aliasing service as well, but have never been able to connect from the same IP as the server; just use localhost for yourself and give out the name to others. In addition I can't connect to the local apache server or anything with it either, never bothered to look up the reason.

[Nykolai Raskaniov]

It's probably a routing / IP forwarding problem somewhere. Check your router settings, perhaps the defaults block too much traffic (like mine) so you have to explicitly create forwarding and allow rules.

[Debci]

can you explain a bit?

regards

[Nykolai Raskaniov]

Most of us have a setup like this:

Home PC(s) - Router & Firewall - Internet

The home PC's have internal IP addresses, non routable, like in RFC 1918 (rfc1918) - Address Allocation for Private Internets.

The router box, which in most cases for home use can also act as a hardware firewall (not extremely powerful of course) is the one which gets the external IP address, from the public pool.

If you set up PS on your own PC, and that uses an internal address like 192.168.2.100, you will not be able to allow others to connect to it from the outside without creating a forwarding rule between your PC and the firewall. In other words if your router has an IP address like 80.80.80.80, you would have to create this rule of the router (via a graphical/web interface or directly on it via the firewall rules if you know the syntax) which forwards packets back and forth between 192.168.2.100 and 80.80.80.80 on UDP port 13331 (or whichever your server is set up on). Also, make sure your own PC as well as the router have the UDP port open.

A possible problem might be if you have dynamically assigned IP and it gets changed by the ISP automatically from time to time. I believe DynDNS could help... Be advised though, this is not a service for a server with heavy traffic.

Fair warning: Please make sure you comply with the ABC license, do not use any of the proprietary content in PS to run a public server.