World: r3wp

208.127.222.200

212 is walmark - when I access it from my work

our Xidys wifi network has C subnet of 193.85.151.*

wait a min.... 208....

ah, that's when you checked it from the website.

193.85.151.2

yes, that is my public IP, and that is IP my worlds are registered 
to ...

the strange "outage" happened 4-6 times in last 6 months ...

scanning older logs... 1 min.

around 11-Nov there was my other outage ...

and 26-Oct

maybe, I would have to search this group for my complaints :-)

I am able to re-register my worlds in 10 minutes, no problem. But 
it would be nice, if our effort would lead to fix of some possible 
problem ....

exactly...

I could make your world as permanent... but then, I'd not know about 
this possible bug.

That was also my motivation to not pay for the world names - yet. 
To find out, what's going on ...

Could you post a script/logic, which decides, if the world is or 
is not online for 10 days?

Maybe you check logs, and maybe when you reboot server, you loose 
the logs? Because - more users reported at the same time the same 
problem.

Well, does not work like that.  The log records the "raw" commands. 
So, it shows right now many hundreds of altme worlds "pinging" that 
they are "live".  The fact that your world never shows "live" is 
a mystery.

And, yes it is true... we rebooted the server recently -- the reason 
your world was "sweeped".

Carl - and here's what happened, but just once. I sent it to feedback 
- very special case:

Hi,


after last outage, I am not able to connect to my worlds - Xidys, 
Vertuzo.


The client even does not try to connect, as I can't see any outgoing 
packets to IP of my world on particular port (Xidys:5402). AltME 
client says - "Xidys exists, but not-online". But - our worlds are 
online. 


When I go to altme.com/check.html, the world seems to be online, 
and the site also is able to connect to it.


So I inspected TCP packets in Wireshark, and it states: "cmd: find 
data: ["Xidys" 0 1.2.17.3.1 4811897].cmd: lookup data: inactive ."

Submitted: 23-Oct-2009/8:52:48-7:00

maybe it is somehow related ...

but maybe it was a client problem, don't know. I had to let my worlds 
to expire and re-register ...

In the TCP packet above, did you edit that text?

anyway ... some food for thoughts. If you need any assistance, or 
anything special I could install on my side, I can help. Other tha 
that, not sure if you want to lose more of your time with it ...

no, no edit IIRC

That packet is not correct.  "].cmd" ?

IIRC I selected "Follow TCP packet" in WireShark, maybe it could 
do some conversions, dunno. Then I did cut and copy ...

Well, as I said, it just happened once. Me, nor my friend on their 
computers were able to connect. The situation was strange, as altme.com/check 
could see worlds both registered, and online ...

If it is not related, I would let it go, I never ever saw it once 
again. Not so worlds outages. Strange you can't see my IP logged?

Well... keep in mind that on your local network, it's a different 
IP.  10.3.0.88 it appears.

What concerns me is that I CAN see your cmd: open -- which is your 
world startup.  But, there are no cmd: live pings.

Hmm, on server I seem to use 1.2(13) - info on splash screen, but 
then client shows 1.2.17

Most of the log contains live pings... millions of them.... but not 
from you.

That means you have the exe .13, but patches to .17 -- that is fine.

What does it mean - live ping? Is it Altme communication type of 
message?

any special ping or behaviour for - live ping? I hope not ... can't 
imagine how it could be blocked here ....

Try this in REBOL:
read dns://wns.altme.com

208.127.222.200

Yes, live ping is just altme packet indicating server is running.

Ok, correct.

BTW, the port is 5502, not 5500.

so, how could it "not to ping" actually?

That is a suprise to me.... I thought it was 5500.

well, you might be lucky, because most of networks don't block outgoing 
connections ... but those who do, will not be able to get to the 
network.

I also always wondered, why proxy does not work, if we have it available 
:-) (but that's different topic)

In the client log, I can see sometimes - wns 26-Oct-2009/9:28:23+1:00 
["find" "Vertuzo" lookup expired]

Ah... good idea. In the log config, add wns-ping monitoring.

how do I add it?