[X] My Assistant

btw, afaik traceroute shows some geographical hints as well. what and eventually how to censor in this case?

Hiding the first few hops?
It's unlikely the problem is there anyway.

If you did a traceroute/mtr, that might actually point towards the problem. A ping only shows there is an issue, not where it is.

Unfortunately, my ISP made it so that anything beyond the 2nd hop always times out. (IMG:[invalid] style_emoticons/default/anime_cry.gif)

Anyway, I'm currently using a VPN, so it's good for now. Hopefully the problem goes away after a while (IMG:[invalid] style_emoticons/default/heh.gif)

btw, afaik traceroute shows some geographical hints as well. what and eventually how to censor in this case?

Well, I'm have no qualms about letting people know my country, so omitting the first 2 hops will do.

Hiding the first few hops?
It's unlikely the problem is there anyway.

Unfortunately, my ISP made it so that anything beyond the 2nd hop always times out. (IMG:[invalid] style_emoticons/default/anime_cry.gif)

Anyway, I'm currently using a VPN, so it's good for now. Hopefully the problem goes away after a while (IMG:[invalid] style_emoticons/default/heh.gif)
Well, I'm have no qualms about letting people know my country, so omitting the first 2 hops will do.

i meant while keeping the overall readability. i know that letting people know your country isn't that big of a deal, but since i'm not too practic with tracert, ipsec and such i just wanted to know what was the maximum level of detail allowed.

if hiding the first few hops until, saying, the first major dataserver (like it's been done until now) is fine enough, then good (IMG:[invalid] style_emoticons/default/happy.gif)

This post has been edited by Scremaz: Sep 9 2017, 16:03

Anyway, I'm currently using a VPN, so it's good for now. Hopefully the problem goes away after a while (IMG:[invalid] style_emoticons/default/heh.gif)
Well, I'm have no qualms about letting people know my country, so omitting the first 2 hops will do.

That basically means your ISP is at fault due to choosing a bad route.

I bet 10 bucks on the DNS server being the real issue.

I bet 10 bucks on the DNS server being the real issue.

I'm using Google DNS so......

I bet 10 bucks on the DNS server being the real issue.

Uh. He's pinging an IP address. DNS is not involved.

Does anybody know in general what the quiet time for server is? I work shiftwork both days and nights so I'm already up all times of the day anyways. Just don't like lag (IMG:[invalid] style_emoticons/default/sad.gif)

You mean a time the game runs faster? For me its in around six hours.

You mean a time the game runs faster? For me its in around six hours.

Yes. Server-side specifically of course. I don't have to worry too much about speed on my side.

So, I did some digging and found a gem called tcp trace route!
Below is the first ever successful tracert in my life!

CODE

Tracing route to 94.100.18.243 [forums.e-hentai.org] on port 80
Over a maximum of 30 hops.
1       2 ms    2 ms    2 ms    192.168.0.1
2       17 ms   22 ms   135 ms
3       16 ms   15 ms   18 ms  
4       24 ms   21 ms   25 ms   10.55.32.118
5       35 ms   32 ms   36 ms   203.169.57.161  [so-2-2-0-xcr1.sng.cw.net]
6       33 ms   29 ms   31 ms   116.51.27.21    [ae-12.r00.sngpsi05.sg.bb.gin.ntt.net]
7       38 ms   34 ms   35 ms   129.250.7.20    [ae-1.r21.sngpsi05.sg.bb.gin.ntt.net]
8       206 ms  205 ms  206 ms  129.250.7.64    [ae-8.r24.londen12.uk.bb.gin.ntt.net]
9       253 ms  303 ms  213 ms  129.250.2.27    [ae-1.r25.londen12.uk.bb.gin.ntt.net]
10      *       431 ms  452 ms  129.250.5.2     [ae-2.r24.amstnl02.nl.bb.gin.ntt.net]
11      418 ms  391 ms  *       129.250.2.113   [ae-1.r02.amstnl02.nl.bb.gin.ntt.net]
12      *       *       430 ms  81.20.64.62     [ae-0.swiftway.amstnl02.nl.bb.gin.ntt.net]
13      673 ms  655 ms  668 ms  94.100.17.251   [251.17.100.94.static.swiftway.net]
14      Destination Reached in 651 ms. Connection established to 94.100.18.243
Trace Complete.

Ehm, ehm, no idea if we even have something like that. Because i think the time i did tell you about is from the player-side. Because after dawn they go to sleep, or something like that.

So, I did some digging and found a gem called tcp trace route!
Below is the first ever successful tracert in my life!

Looks like it's routing over NTT, who seem to have a broken route between London and Amsterdam. You can download a program called WinMTR that will give you something more useful, which you can send to your ISP.

Also, ew, carrier NAT.

Uh. He's pinging an IP address. DNS is not involved.

Working like crazy for my exams really tires me out... (IMG:[invalid] style_emoticons/default/faint.gif)

lol. i just did one as well out of curiosity. my first expired request is just after the router (IMG:[invalid] style_emoticons/default/laugh.gif)

past that, all's fine. prior to 0.85 patch it was way worse.

lol. i just did one as well out of curiosity. my first expired request is just after the router (IMG:[invalid] style_emoticons/default/laugh.gif)

It's normal that some nodes don't respond during an MTR/traceroute, that just means they have been configured to not do so. As long as there are no dropped packets on the following nodes, you can usually assume that hop is fine.

It's normal that some nodes don't respond during an MTR/traceroute, that just means they have been configured to not do so. As long as there are no dropped packets on the following nodes, you can usually assume that hop is fine.

yes, that's the only excluded hop. and guess that having that one completely not answering (three asterisks) is also the reason because it doesn't give me this line: "14 Destination Reached in 651 ms. Connection established to 94.100.18.243", right?

yes, that's the only excluded hop. and guess that having that one completely not answering (three asterisks) is also the reason because it doesn't give me this line: "14 Destination Reached in 651 ms. Connection established to 94.100.18.243", right?

tcptraceroute does not work the same as tracert that comes with Windows. The former uses TCP; the latter uses ICMP, and doesn't establish a connection as such.

oh, it's a whole different thing. and actually, also LOL said so. does make sense, thank you.

Looks like it's routing over NTT, who seem to have a broken route between London and Amsterdam. You can download a program called WinMTR that will give you something more useful, which you can send to your ISP.

Also, ew, carrier NAT.

Thanks for the insight.

My situation seems to be improving though. At least now I'm no longer getting timeouts when accessing the forums.