Silly question, how are you determining online status?
I see connection attempts without a userid in the serverlog. could be that?
Hopefully that is it. Cause I know for me, if I were to decide to make my server info public, anything on another port wouldn't get a response. (Or would get the wrong machine if you got lucky and hit the port my MUD runs on.)
Rollback Post to RevisionRollBack
Tis far better to be a witty fool than a foolish wit.
The method for checking if you're currently online is indeed simply querying the server. It's pretty poor but it's the only way currently, unless you guys wanted to run a service provided by me for providing heartbeats, but a) I cba and :cool.gif: I doubt you'd trust it.
So yeah, you'll see connections from my server quite a lot, every 120 seconds while it's online. If this aint cool I can drop it.
also re: ip/hostname, this is only a very temporary solution, I don't have time (or the energy) to deal with the **** associated with hostnames over IPs, IPs are much easier to handle. If this is still being used in a few weeks I'll look into enabling hostnames.
also re: ip/hostname, this is only a very temporary solution, I don't have time (or the energy) to deal with the **** associated with hostnames over IPs, IPs are much easier to handle. If this is still being used in a few weeks I'll look into enabling hostnames.
Since it looks like you are using PHP here is a quick 'n dirty to convert to an IP string:
it currently does monitor ping (it's logged with historic data) but the ping is done from my server, not your client. So I could guess based on your connection to my server and my connection to theirs, but it's not possible to do it accurately.
You should probably allow hamachi servers to put their IP into your list, show them as something different than green/red (since your site probably can't check a networked server to see if it's online), and have the people entering it to input the network/password details.
Some, like myself, can't host normally without it, for some unknown reason.
Ok little tip for all you folks who keep posting local IPs
If it starts in:
192.168.
It isn't a public IP and we CANNOT connect using it. (You however can and should use that IP for connecting to your own server.)
We need the public one. (And the public one is probably NOT going to work when YOU try it from your local network.)
Rollback Post to RevisionRollBack
Tis far better to be a witty fool than a foolish wit.
http://mcserverlist.net
Hopefully that is it. Cause I know for me, if I were to decide to make my server info public, anything on another port wouldn't get a response. (Or would get the wrong machine if you got lucky and hit the port my MUD runs on.)
Not surprised.
So yeah, you'll see connections from my server quite a lot, every 120 seconds while it's online. If this aint cool I can drop it.
also re: ip/hostname, this is only a very temporary solution, I don't have time (or the energy) to deal with the **** associated with hostnames over IPs, IPs are much easier to handle. If this is still being used in a few weeks I'll look into enabling hostnames.
Edit: Just saw the post about hostnames, that sucks :/
Type in 127.0.0.1 from the computer you are hosting the server on and see if it's even running.
184.96.254.213
Time up. Whenever.
Since it looks like you are using PHP here is a quick 'n dirty to convert to an IP string:
With the regex in there it will catch strings that are already IPs and leave them alone.
it currently does monitor ping (it's logged with historic data) but the ping is done from my server, not your client. So I could guess based on your connection to my server and my connection to theirs, but it's not possible to do it accurately.
127.0.0.1 is an internal IP. It defines your computer on your personal network. You have a different IP when other people connect to you.
Some, like myself, can't host normally without it, for some unknown reason.
If it starts in:
192.168.
It isn't a public IP and we CANNOT connect using it. (You however can and should use that IP for connecting to your own server.)
We need the public one. (And the public one is probably NOT going to work when YOU try it from your local network.)