World: r3wp

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?

the beacon - should be done by my client, or my server? I mean - 
I could install Wireshark, and filter for packets on port 5500, to 
see, if it "pings"

1 min

in altme/prefs/prefs.txt, add the line:

debug: [events: [boot error note start halt wns wns-ping]]

on my client, or the server?

server... but, wait a min...

should I restart my servers?

actually, it's:  altme/prefs/debug  (no suffix, but as a text file)
Then, in that file:

events: [boot error ... above list  ]

restart just one server

so should I delete the debug line from prefs.txt?

btw, altme will notice the debug file, and rewrite it with all debug 
fields

correct, remove that line.

done - world Vertuzo restarted, Xidys runs the old way. Vertuzo runs 
on port 5402

sorry, vertuzo is 5401

is it running?

yes, it is ...

I can connect from remote client

I wonder how that is possible?

The log does not show that the world started. So, there is a problem 
on port 5502.

outgoing port 5502?

yes.

wait... nevermind. That's for an experimental build.