Llynara Report post Posted February 2, 2023 (edited) I didn't see a topic started yet for the tracert logs Radu asked for, so I'm starting one here. Not sure it's in the right forum. Feel free to move/merge/etc as needed. Thanks, Llyn Here are three traces I did during lags in the past hour: Edited to add: I have Starlink if that matters Tracing route to game.eternal-lands.com [192.99.21.222] over a maximum of 30 hops: 1 1 ms 28 ms 1 ms 192.168.1.1 2 32 ms 50 ms 47 ms 100.64.0.1 3 80 ms 52 ms 67 ms 172.16.252.92 4 64 ms 51 ms 61 ms undefined.hostname.localhost [206.224.65.132] 5 90 ms 56 ms 67 ms undefined.hostname.localhost [206.224.64.101] 6 47 ms 32 ms 38 ms chi-b24-link.telia.net [213.248.91.206] 7 44 ms 61 ms 44 ms chi-b23-link.ip.twelve99.net [62.115.138.54] 8 57 ms 72 ms 53 ms chi-5-a9.il.us [142.44.208.208] 9 69 ms 73 ms 84 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140] 10 * * * Request timed out. 11 78 ms 57 ms 57 ms be50-7.bhs-3b-a9.qc.ca [198.27.73.98] 12 59 ms 65 ms 73 ms game.eternal-lands.com [192.99.21.222] Trace complete. C:\Users\Kim>tracert game.eternal-lands.com Tracing route to game.eternal-lands.com [192.99.21.222] over a maximum of 30 hops: 1 <1 ms 4 ms <1 ms 192.168.1.1 2 45 ms 41 ms 48 ms 100.64.0.1 3 30 ms 37 ms 45 ms 172.16.252.92 4 49 ms 30 ms 46 ms undefined.hostname.localhost [206.224.65.132] 5 35 ms * 34 ms undefined.hostname.localhost [206.224.64.101] 6 37 ms 30 ms 30 ms chi-b24-link.telia.net [213.248.91.206] 7 27 ms 28 ms 33 ms chi-b23-link.ip.twelve99.net [62.115.138.54] 8 199 ms 52 ms 52 ms chi-5-a9.il.us [142.44.208.208] 9 60 ms 61 ms 62 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140] 10 * * * Request timed out. 11 64 ms 82 ms 60 ms be50-7.bhs-3b-a9.qc.ca [198.27.73.98] 12 64 ms 64 ms 62 ms game.eternal-lands.com [192.99.21.222] Trace complete. C:\Users\Kim>tracert game.eternal-lands.com Tracing route to game.eternal-lands.com [192.99.21.222] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 37 ms 32 ms 35 ms 100.64.0.1 3 44 ms 54 ms 29 ms 172.16.252.92 4 45 ms 48 ms 40 ms undefined.hostname.localhost [206.224.65.132] 5 34 ms 37 ms 46 ms undefined.hostname.localhost [206.224.64.101] 6 49 ms 44 ms 37 ms chi-b24-link.telia.net [213.248.91.206] 7 35 ms 41 ms 39 ms chi-b23-link.ip.twelve99.net [62.115.138.54] 8 48 ms 53 ms 60 ms chi-5-a9.il.us [142.44.208.208] 9 64 ms 53 ms 57 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140] 10 * * * Request timed out. 11 56 ms 65 ms 45 ms be50-7.bhs-3b-a9.qc.ca [198.27.73.98] 12 63 ms 50 ms 55 ms game.eternal-lands.com [192.99.21.222] Trace complete. Edited February 2, 2023 by Llynara Quote Share this post Link to post Share on other sites
Ozmondius Report post Posted February 2, 2023 Quote Share this post Link to post Share on other sites
Entropy Report post Posted February 2, 2023 From Nadziak: https://ibb.co/xCMwSZX Quote Share this post Link to post Share on other sites
revi Report post Posted February 4, 2023 two traceroutes from tonight: First, I'd say normal for me: Quote traceroute to game.eternal-lands.com (192.99.21.222), 30 hops max, 60 byte packets 1 lan.home (192.168.1.1) 0.458 ms 0.499 ms 0.528 ms 2 80.10.234.201 (80.10.234.201) 2.703 ms 2.666 ms 2.742 ms 3 80.12.192.254 (80.12.192.254) 2.878 ms 2.841 ms 2.963 ms 4 ae79-0.ncnan202.rbci.orange.net (193.253.151.14) 3.258 ms 3.336 ms 3.299 ms 5 ae47-0.nridf202.rbci.orange.net (193.252.162.246) 9.186 ms 9.149 ms 9.196 ms 6 ae43-0.noidf002.rbci.orange.net (193.252.98.238) 9.551 ms 8.185 ms 8.241 ms 7 be104-202.par-gsw-pb1-nc5.fr.eu (37.187.36.22) 8.400 ms 8.456 ms 8.635 ms 8 * * * 9 * * * 10 * * * 11 be102.rbx-g2-nc5.fr.eu (94.23.122.214) 13.277 ms 13.234 ms be102.rbx-g1-nc5.fr.eu (94.23.122.146) 138.049 ms 12 lon-thw-sbb1-nc5.uk.eu (54.36.50.240) 17.379 ms 16.026 ms 15.905 ms 13 nyc-ny1-sbb1-8k.nj.us (192.99.146.127) 90.126 ms nyc-ny1-sbb2-8k.nj.us (192.99.146.133) 86.617 ms 86.558 ms 14 be102.bhs-g2-nc5.qc.ca (192.99.146.138) 93.513 ms 91.615 ms 91.188 ms 15 * * * 16 be50-5.bhs-3b-a9.qc.ca (198.27.73.96) 93.234 ms be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 91.071 ms be50-5.bhs-3b -a9.qc.ca (198.27.73.96) 91.442 ms 17 game.eternal-lands.com (192.99.21.222) 91.774 ms 90.377 ms 89.762 ms A bit later: Quote traceroute to game.eternal-lands.com (192.99.21.222), 30 hops max, 60 byte packets 1 lan.home (192.168.1.1) 0.429 ms 0.496 ms 0.557 ms 2 80.10.234.201 (80.10.234.201) 3.269 ms 3.248 ms 3.227 ms 3 80.12.192.254 (80.12.192.254) 3.207 ms 3.272 ms 3.251 ms 4 ae79-0.ncnan202.rbci.orange.net (193.253.151.14) 3.674 ms 3.652 ms 3.718 ms 5 ae47-0.nridf202.rbci.orange.net (193.252.162.246) 9.268 ms 9.246 ms 9.335 ms 6 ae43-0.noidf002.rbci.orange.net (193.252.98.238) 9.505 ms 8.677 ms 9.315 ms 7 be104-202.par-gsw-pb1-nc5.fr.eu (37.187.36.22) 366.158 ms 362.097 ms 362.148 ms 8 * * * 9 * * * 10 * * * 11 be102.rbx-g2-nc5.fr.eu (94.23.122.214) 14.075 ms be103.rbx-g4-nc5.fr.eu (54.36.50.229) 11.737 ms be103.rbx-g3 -nc5.fr.eu (54.36.50.227) 12.440 ms 12 lon-thw-sbb1-nc5.uk.eu (54.36.50.240) 15.775 ms lon-drch-sbb1-nc5.uk.eu (54.36.50.230) 15.513 ms 15.143 ms 13 * * * 14 be102.bhs-g1-nc5.qc.ca (198.27.73.204) 93.261 ms 91.424 ms be102.bhs-g2-nc5.qc.ca (192.99.146.138) 92.528 ms 15 * * * 16 be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 93.096 ms 96.039 ms 93.135 ms 17 game.eternal-lands.com (192.99.21.222) 88.393 ms 91.610 ms 89.042 ms that one was close to a moment where a number of bots grued. The IP 37.187.36.22 is from OVH SAS, as are all the IPs after that one... Quote Share this post Link to post Share on other sites
Biker_Boy Report post Posted February 4, 2023 Tracing route to 192.99.21.222 50 bytes from 192.99.21.222: time=146 ms 1 1 1 192.168.200.1 home.Home 2 26 25 72.253.4.3 3 90 64 206.72.210.38 net-data-centers.as558.any2ix.coresite.com 4 * * timed out 5 110 20 192.99.146.128 dfw-da2-sbb1-8k.tx.us 6 * * timed out 7 177 67 178.32.135.152 be100-1241.chi-5-a9.il.us 8 190 13 192.99.146.140 be103.bhs-g2-nc5.qc.ca 9 * * timed out 10 171 -19 198.27.73.98 be50-7.bhs-3b-a9.qc.ca 11 146 -25 192.99.21.222 game.eternal-lands.com host reached Seems to start timing out after hop 3 for me, first 3 hops totally stable all after that one fail intermittently. Quote Share this post Link to post Share on other sites
Guest annah Report post Posted February 4, 2023 timestamps when latest grues occurred; 2023-02-04 18:55:04 UTC 2023-02-04 19:12:06 UTC 2023-02-04 19:29:10 UTC 2023-02-04 19:46:46 UTC 2023-02-04 20:05:58 UTC 2023-02-04 20:23:22 UTC 2023-02-04 20:56:06 UTC 2023-02-04 21:13:41 UTC which translates to them being ['1022s', '1024s', '1056s', '1152s', '1044s', '1964s', '1056s'] seconds apart from each other Quote Share this post Link to post Share on other sites
Guest annah Report post Posted February 5, 2023 grue timestamps and lost packets log, all times are UTC Sat Feb 4 23:32:55 2023 [1675553575.432805] no answer yet for icmp_seq=1602 +21pkts lost; 1060 sec since last burst end; 1089 sec since last burst start Sat Feb 4 23:50:30 2023 [1675554630.664790] no answer yet for icmp_seq=2656 +17pkts lost; 1028 sec since last burst end; 1055 sec since last burst start Sun Feb 5 00:07:35 2023 [1675555655.240799] no answer yet for icmp_seq=3679 +18pkts lost; 996 sec since last burst end; 1025 sec since last burst start Sun Feb 5 01:16:22 2023 [1675559782.536802] no answer yet for icmp_seq=7802 +18pkts lost; 4100 sec since last burst end; 4127 sec since last burst start Sun Feb 5 01:33:27 2023 [1675560807.752804] no answer yet for icmp_seq=8826 +17pkts lost; 998 sec since last burst end; 1025 sec since last burst start Sun Feb 5 01:50:30 2023 [1675561830.217801] no answer yet for icmp_seq=9847 +23pkts lost; 995 sec since last burst end; 1022 sec since last burst start Sun Feb 5 02:07:02 2023 [1675562822.600803] no answer yet for icmp_seq=10838 +20pkts lost; 964 sec since last burst end; 992 sec since last burst start Sun Feb 5 02:24:38 2023 [1675563878.216801] no answer yet for icmp_seq=11892 +23pkts lost; 1027 sec since last burst end; 1056 sec since last burst start Sun Feb 5 02:57:10 2023 [1675565830.408799] no answer yet for icmp_seq=13842 +20pkts lost; 1923 sec since last burst end; 1952 sec since last burst start Sun Feb 5 03:14:16 2023 [1675566856.712804] no answer yet for icmp_seq=14867 +18pkts lost; 997 sec since last burst end; 1026 sec since last burst start Sun Feb 5 03:31:18 2023 [1675567878.216799] no answer yet for icmp_seq=15887 +17pkts lost; 997 sec since last burst end; 1022 sec since last burst start Sun Feb 5 03:48:23 2023 [1675568903.432802] no answer yet for icmp_seq=16911 +21pkts lost; 997 sec since last burst end; 1025 sec since last burst start Sun Feb 5 04:05:59 2023 [1675569959.752804] no answer yet for icmp_seq=17966 +18pkts lost; 1029 sec since last burst end; 1056 sec since last burst start Sun Feb 5 04:52:45 2023 [1675572765.321802] no answer yet for icmp_seq=20769 +24pkts lost; 2778 sec since last burst end; 2806 sec since last burst start Sun Feb 5 05:11:23 2023 [1675573883.592794] no answer yet for icmp_seq=21886 +22pkts lost; 1089 sec since last burst end; 1118 sec since last burst start Sun Feb 5 05:32:44 2023 [1675575164.040801] no answer yet for icmp_seq=23165 +20pkts lost; 1251 sec since last burst end; 1280 sec since last burst start Sun Feb 5 05:51:34 2023 [1675576294.344801] no answer yet for icmp_seq=24294 +18pkts lost; 1103 sec since last burst end; 1130 sec since last burst start Sun Feb 5 06:09:43 2023 [1675577383.560806] no answer yet for icmp_seq=25382 +21pkts lost; 1061 sec since last burst end; 1089 sec since last burst start Sun Feb 5 06:27:51 2023 [1675578471.689805] no answer yet for icmp_seq=26469 +14pkts lost; 1060 sec since last burst end; 1088 sec since last burst start Sun Feb 5 06:48:39 2023 [1675579719.240790] no answer yet for icmp_seq=27715 +21pkts lost; 1219 sec since last burst end; 1248 sec since last burst start Sun Feb 5 07:06:47 2023 [1675580807.560800] no answer yet for icmp_seq=28802 +21pkts lost; 1059 sec since last burst end; 1088 sec since last burst start Sun Feb 5 07:24:57 2023 [1675581897.160790] no answer yet for icmp_seq=29890 +22pkts lost; 1062 sec since last burst end; 1090 sec since last burst start Sun Feb 5 07:43:36 2023 [1675583016.392800] no answer yet for icmp_seq=31008 +22pkts lost; 1093 sec since last burst end; 1119 sec since last burst start Sun Feb 5 08:03:07 2023 [1675584187.912802] no answer yet for icmp_seq=32178 +20pkts lost; 1144 sec since last burst end; 1172 sec since last burst start Sun Feb 5 09:57:27 2023 [1675591047.112803] no answer yet for icmp_seq=39032 +4pkts lost; 6851 sec since last burst end; 6859 sec since last burst start Sun Feb 5 10:56:26 2023 [1675594586.120808] no answer yet for icmp_seq=42568 +10pkts lost; 3525 sec since last burst end; 3539 sec since last burst start Sun Feb 5 11:13:31 2023 [1675595611.336804] no answer yet for icmp_seq=43592 +20pkts lost; 996 sec since last burst end; 1025 sec since last burst start Sun Feb 5 11:31:38 2023 [1675596698.696803] no answer yet for icmp_seq=44678 +23pkts lost; 1060 sec since last burst end; 1087 sec since last burst start Quote Share this post Link to post Share on other sites
caladina Report post Posted February 5, 2023 with the lags, if i'm moving i just lag for a few seconds if i'm afk or stopped moving i grue and disconnect, while its mildly annoying few days back when i had three afk for recovering some ap they had all grued and disconnected which now looks like it was that that lead to the el files being corrupted and having to make a new file. when i was playing this client and on the same comp (macbook 2021) i never had any grue / disconnects Quote Share this post Link to post Share on other sites
revi Report post Posted February 5, 2023 8 minutes ago, caladina said: when i was playing this client and on the same comp (macbook 2021) i never had any grue / disconnects Grues shouldn't depend on your computer. They are a network problem, so while you may suffer a disconnect due to your home network, that's rather unlikely. If you get disconnected due to your computer, you'll have to get your network card checked... As for a grue corrupting el files: again, not likely, as a grue doesn't close the client. The more likely cause is that you closed several clients in a very short time. That's an advantage of the old system of running multiple clients (through lines in "server.lst"): all config files are separate... Quote Share this post Link to post Share on other sites
Guest annah Report post Posted February 7, 2023 https://imgur.com/uIf3y5z https://zerobin.net/?aa8950ed1fbe54ce#lkQIB3K07a6KEfUr4TSY8Zfcxq6xVmPe99lw5KQPKUs= Quote Share this post Link to post Share on other sites
revi Report post Posted February 7, 2023 Quote My traceroute [v0.92] manticore (192.168.1.14) 2023-02-07T20:33:53+0100 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. lan.home (192.168.1.1) 0.0% 167 0.5 0.5 0.4 4.3 0.4 2. 80.10.234.201 (80.10.234.201) 0.0% 167 2.2 2.1 1.6 3.5 0.3 3. 80.12.192.254 (80.12.192.254) 0.6% 167 2.4 2.2 1.5 5.3 0.5 4. ae79-0.ncnan202.rbci.orange.net (193.253.151.14) 0.0% 167 2.4 3.6 1.7 24.0 3.4 5. ae47-0.nridf202.rbci.orange.net (193.252.162.246) 0.0% 167 7.8 8.0 7.3 14.3 0.6 6. ae43-0.noidf002.rbci.orange.net (193.252.98.238) 0.0% 167 7.5 8.1 7.5 12.8 0.7 7. be104-202.par-gsw-pb1-nc5.fr.eu (37.187.36.22) 0.0% 166 179.5 63.2 7.8 408.6 92.0 8. ??? 9. ??? 10. ??? 11. be103.rbx-g4-nc5.fr.eu (54.36.50.229) 0.0% 166 11.1 18.7 11.0 290.7 34.4 12. lon-drch-sbb1-nc5.uk.eu (54.36.50.230) 0.0% 166 15.0 15.6 14.8 19.3 0.5 13. nyc-ny1-sbb2-8k.nj.us (192.99.146.133) 62.0% 166 86.7 86.6 84.8 88.5 0.7 14. be102.bhs-g2-nc5.qc.ca (192.99.146.138) 0.0% 166 92.5 101.0 91.7 296.0 27.8 15. ??? 16. be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 0.0% 166 94.2 94.0 93.2 97.9 0.6 17. game.eternal-lands.com (192.99.21.222) 0.0% 166 91.8 91.7 90.9 95.2 0.5 The above is a normal MRT output. Lines 2-6 are from my ISP, lines 7-14 and 16-17 are on OVH IPs. The 60+% pacage loss was constant over the afternoon, and when trying with tcp packets, that node still gave 50% package loss A previous run ended up showing a host for line 15 with 100% packet loss: Quote 195-154-77-110.rev.poneytelecom.eu (195.154.77.110) the host in that abberrant line 15 seems to be from "Online S.A.S" Quote Share this post Link to post Share on other sites
Guest annah Report post Posted February 8, 2023 https://imgur.com/9MItYog My traceroute [v0.95] LV-1201 (192.168.3.179) -> game.eternal-lands.com (192.99.21.222) 2023-02-08T15:29:18+0100 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Drop Snt Loss% Last Best Avg Wrst StDev Gmean Javg Jttr Jmax 3. 155.133.104.22 (155.133.104.22) 1 18360 0.0% 9.9 8.9 9.0 163.6 2.9 9.0 1.0 0.3 154. 4. 155.133.104.1 (155.133.104.1) 1672 18360 9.1% 10.8 9.6 9.7 206.6 2.3 9.6 0.9 0.1 196. 5. (waiting for reply) 6. (waiting for reply) 7. (waiting for reply) 8. (waiting for reply) 9. fra-fr5-sbb2-nc5.de.eu (54.36.50.116) 54 18360 0.3% 25.6 23.9 24.1 267.8 4.2 24.1 1.7 0.5 243. 10. be103.rbx-g2-nc5.fr.eu (94.23.122.240) 27 18360 0.1% 33.4 31.9 50.1 414.8 53.4 38.7 35.2 0.5 382. 11. (waiting for reply) 12. nyc-ny1-sbb2-8k.nj.us (192.99.146.133) 1117 18360 60.9% 106.4 103.4 104.7 263.7 3.2 104.7 1.6 0.5 158. 13. be102.bhs-g2-nc5.qc.ca (192.99.146.138) 4 18360 0.0% 112.1 110.7 112.4 378.0 23.2 111.8 16.6 0.4 266. 14. (waiting for reply) 15. be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 3 18360 0.0% 111.8 110.3 110.5 328.0 4.2 110.5 2.1 0.7 216. 16. game.eternal-lands.com (192.99.21.222) 201 18359 1.1% 114.7 113.6 113.9 304.8 2.6 113.9 0.9 0.4 189. Quote Share this post Link to post Share on other sites
