World: r3wp

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.

It's 5500 as documented.

I try to look at netstat -an on that machine, but nothing obvious 
....

look at log file.

btw - debug file did not change ...

servers/vertuzo/log.txt?

yes

look for line that begins with wns

nothing logged ...

altme/prefs/debug (no suffix), added following line:

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

is that correct? Then I restarted one world - Vertuzo, port 5401

verifying, 1 min

ok, my mistake. Servers don't use the normal client prefs. Here are 
the steps...

move your debug file to the altme/servers/vertuzo directory, then 
restart the world

btw, remove the debug file from your other dir, or your clients may 
log too much info

After startup, debug file is:
; AltME Debugging and Logging Options
debug: 0
file: %log.txt
events: [boot error note start halt wns wns-ping]
echo: none
net: none
time: none

log.txt shows:
...
wns 28-Dec-2009/16:12:29-8:00 ["open" "testtest" 5400]
wns 28-Dec-2009/16:12:31-8:00 ["close" "testtest" lookup ok]
wns-ping 28-Dec-2009/16:13:31-8:00 [open]
wns-ping 28-Dec-2009/16:13:31-8:00 [lookup]

debug rewritten, good sign ...

WNS log shows:

command 28-Dec-2009/16:12:30-8:00 [75.101.29.32 {cmd: open data: 
["testtest" 0]}]

command 28-Dec-2009/16:13:31-8:00 [75.101.29.32 {cmd: live data: 
["testtest" 64#{OD...}]}]

start 29-Dec-2009/1:12:59+1:00 ["vertuzo" 5401 1.2.13 29-Dec-2009/1:12:59+1:00]

So, this indicates that it works (from here).

log.txt shows no more detail though ...

Ah... very interesting...

my log.txt shows:

start 28-Dec-2009/16:12:29-8:00 ["testtest" 5400 1.2.18 28-Dec-2009/16:12:29-8:00]

so, version number is different.