Here is a traceroute from Storm Haven:
Code:
traceroute eqemulator.org
traceroute to eqemulator.org (67.23.190.71), 30 hops max, 40 byte packets
1 DD-WRT (192.168.1.1) 0.575 ms 0.833 ms 1.692 ms
2 10.167.160.1 (10.167.160.1) 10.798 ms 11.767 ms 12.060 ms
3 96-34-52-44.static.unas.mo.charter.com (96.34.52.44) 12.246 ms 12.372 ms 12.472 ms
4 96-34-48-57.static.unas.mo.charter.com (96.34.48.57) 16.408 ms 17.219 ms 17.501 ms
5 96-34-2-194.static.unas.mo.charter.com (96.34.2.194) 17.683 ms 17.780 ms 17.877 ms
6 96-34-0-130.static.unas.mo.charter.com (96.34.0.130) 33.103 ms 27.883 ms 28.071 ms
7 96-34-2-123.static.unas.mo.charter.com (96.34.2.123) 31.412 ms 29.735 ms 32.252 ms
8 96-34-78-89.static.kgpt.tn.charter.com (96.34.78.89) 33.349 ms 33.782 ms 96-34-72-5.static.unas.mo.charter.com (96.34.72
.5) 33.636 ms
9 96-34-72-39.static.unas.mo.charter.com (96.34.72.39) 38.576 ms 96-34-72-37.static.unas.mo.charter.com (96.34.72.37) 38.2
32 ms 96-34-78-33.static.kgpt.tn.charter.com (96.34.78.33) 37.299 ms
10 dtr02spbgsc-tge-2-3.spbg.sc.charter.com (96.34.64.40) 38.731 ms 38.865 ms 38.969 ms
11 96-34-67-181.static.unas.sc.charter.com (96.34.67.181) 39.294 ms 39.414 ms 39.499 ms
12 96-34-67-179.static.unas.sc.charter.com (96.34.67.179) 47.360 ms 48.357 ms 48.467 ms
13 96-34-67-175.static.unas.sc.charter.com (96.34.67.175) 36.332 ms 34.701 ms 37.690 ms
14 68-115-195-86.static.spbg.sc.charter.com (68.115.195.86) 39.402 ms 39.257 ms 39.486 ms
15 te-5-5.rtr2.avl1.netriplex.com (67.23.161.254) 38.752 ms 39.037 ms 42.180 ms
16 eqemulator.net (67.23.190.71) 43.860 ms 43.474 ms 43.192 ms
XXXX@stormhaven:~$
Not sure that will be of any assistance though. I haven't noticed any packet loss during continuous pings while the problem is happening. I do agree that better LS connectivity logging might help to isolate problems like this. Heck, for all I know, it could be my server that started the eqemu website server list to start having status display issues. Though if that was the case, it could mean that any server could have potentially caused it for all which would be a good thing to resolve/prevent anyway.
My best guess so far is that the problem is somehow related to the fairly new (6 months old or so) code that allows servers to connect to multiple Login Servers at the same time. I know that when I removed the config to connect to LSs other than the EQEmu one, my server was suddenly able to stay connected to the EQEmu LS much better.
And, Rogean, I don't mean to seem like I am pushing this issue all on you or anything. It is just hard to figure out a connection issue only looking at a single side of the connection. If there didn't seem to be any other oddities going on, I would assume that the problem was on my end only and would work on it quietly by myself until it was resolved. Since it seems that it may not just be my server, it doesn't hurt to investigate the possibility of the issue being with the EQEmu LS or even one of the other LS like tsahosting.net or peqtgc.net.
I am curious if one of the other LSs was disconnecting servers, maybe they would try to reconnect to all LSs they are configured to connect to even if they are already connected? I should check with Gaeorn to see if he is seeing anything odd on tsahosting.net lately.