World: r3wp

It has to be open - I am right now on my own network.

It ran OK ... my public IP is - 193.85.151.2

In one case, I also notice bug with backport connection from altme.com. 
I mean - when trying to start 2 servers on one machine. It registered 
second world on the same port .... but I don't remember it exactly 
...

maybe all you need Pekr is a script that pings safeworlds on port 
5500

Graham - no, that requirement is not there, and should not be there.

Wow i'ts cheating :-)

Xidys shows no server pings.

I think, that altme.com stops pinging, or at some point mistakenly 
decides, that my worlds are not online for more than 10 days, and 
frees the names. That is the part I would try to look for the bug 
...

Pekr doesn't want solutions .. he wants a perrmanent fix

Graham - if I would want a solution, I would pay few bucks for permanent 
registration and be done with it ... = noone would complain about 
apparent bug.

Pekr, your client is pinging safeworlds .. they're not pinging you!

Carl - what do you mean by "ping"?

There is no such requirement in the docs!

Yes, there is.

don't tell me you can't ping 193.85.151.2

Pekr, does wireshark show any contact with the homeworld ..??

Explanation: worlds know your IP because you send it to SafeWorlds 
server every 5 mins.

Altme must be calling home regularly so that mum knows you're alive 
and not to release your name

This also allows dynamic IPs to operate.

This is also used to "lock" the world name from reuse.

If I am online with 2 worlds right now, being connected to Xidys 
now = ports are OK

It's a heartbeart every 5 mins

So just tell me, what your "ping" means ...

Normal ping to public (registered/sent) IP adress?

But if you run more than one world on the same IP address .. the 
"ping" must be also sending the world name

Or you need DST NAT 5500 back to my world servers?

Graham - no, wrong - the "ping" is sending IP and port ...

Yes, it sends world name and a hash key to authenticate your claim.

hmm, maybe even the name, but it does not matter ...

Carl - to proceed - you said you can't ping Xidys ... what does it 
mean?

ping to public IP? Should work.

so does wireshark show that your altme sever is doing this??

Or you need 5500 port being accessible to your server?

You do not need 5500 inbound. Only outbound.

Xidys Altme server -- ( every 5 mins ) ---> safeworlds:5500

Graham - doing what? ;-) My worlds are running, clients connected, 
so yes, my world is doing it :-)

Well, then everything is ok on my side. So why you are saying that 
you can't ping Xidys?

What I said above was that if I grep the log, I do not see a "live" 
message from your server.

Graham - if port 5500 would not work, I think that altme name translation 
would not work ...

Pekr, you don't understand

safeworlds is not contacting you ...

wait a minute, maybe I have to kill someone :-)

Carl - can you see any 193.85.151.* IP in there?

maybe your firewall is blocking this heartbeat ?

yes

My brother put public IPs also on some subsequent routers.

so actually it might come out from different public address ...

ah

I mean - being NATted to different public address ...

I was wondering about that.