World: r3wp

There has to be some bug somewhere ...

Did you pay for your worlds Pekr?

Graham - no.

I am trying to track down a nasty bug, not a business model

So it appears to be only an issue with unpaid worlds?

me too ...

Pekr, are you using AltServe or AtlME?

AltME only ...

So, you use AltME for both server and client.

But I can guarantee, that the worlds are used. I was online the same 
day, and in few hours, worlds were not accessible, and altme.com/check 
stated world names being available. That should not happen.

Note that AltME when used as a server must be able to ping port 5500 
at regular intervals. That's how Safeworlds keeps your world registered.

If the Safeworlds server does not see the ping, then it cannot reset 
the timer on your world.

yes, I run 50 mikrotik routers, I know what I am doing :-) But - 
you say I need to open port 5500 INTO my network?

There are only two ways this can happen (that I can think of):
1. you have 5500 blocked (outgoing)

2. you are using AltServe (not AltME) and it does not ping (because 
it is commerical)

I just don't know how to track it down. The only thing I can follow 
is docs, which state, that altme.com tries for 10 days ... but it 
is not the case.

Try this in REBOL:
close open tcp://www.safeworlds.com:5500

everything enablet (outgouing)

I can grep the log... 1 min.

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??