Why some IP address from Thailand cannot go to GTRU
-
-
Are you with 3bb by any chance?
I live in Thailand too, and myself, and 2 other friends living in totally different regions / provinces… have experienced the same issue with 3bb.
They even came to the house, and what joy (in front of three straight Thai """technicians""") to have to type on the screen www.gaytorrent.ru and show them that it couldn't connect, and on THAT day, neither would www.gay-torrents.org, nor www.gay-torrents.net …yet, of course, no problem with other sites.
I SHOWED them, that on my tablet... (DTAC) there was NO PROBLEM accessing the sites, so it was clear this wasn't the Thai government doing a blockade.
They left the house scratching their heads, not saying ANYTHING to me.
After not hearing from them for 2 more days... I finally bit the bullet and signed up with a VPN... and NO PROBLEM accessing the site, via VPN.
The VERY NEXT DAY, I discovered I could once again access the site with 3bb.
They called me to ask if my problem had gone away, and I had to say yes, thank you, and all that.
Well, big surprise, the VERY NEXT DAY... SAME PROBLEM. Could NOT log in with 3bb, and neither could my friend.
So now... a month later... it has developed the distinct pattern where... sometimes it works... and sometimes it doesn't.
Dealing with their tech service... they're likely to show you screen dumps "proving" that using the DOS COMMAND of tracert... the connection is failing, and point the finger at GTRU.
News flash... due to site protection designs... involving DoS attacks and more... the "tracert www.gaytorrent.ru" command ALWAYS FAILS, regardless of whether or not it's a "good day" (can connect to GTRU w/o issue) or a "bad day". So that's a bullshit "proof" excuse (lie) that they will try to pull, yet good luck explaining THAT to their """technical""" staff :blink:
All in all… connecting or not connecting...? ...it seems totally random; I cannot seem to form a pattern to this. But when I cannot connect, my other friends with 3bb cannot connect, too.
I HAVE seen that sometimes, when connecting (good day) with 3bb, the pictures in the torrent display will NOT show, and same with my friends.
I have also experimented, and found some evidence that if I use the VPN to log in... sometimes I can turn the VPN OFF, and continue navigating within the site... but still testing this...
Anyway, in conclusion, I'd say 3bb had different internal routing schemes that they switch to... and some of them work, and some of them don't... and I wouldn't hold my breath for them to fix the issue.
If your ISP is NOT 3bb, well, so sorry, then I'd have to say that perhaps... none of the above applies directly to you? ...but not sure.
I'd keep in mind that the Thai government HAS shown conclusive evidence that they are working towards a "Single Gateway" for ALL of Thai Internet communications, ostentatiously to "improve" services, but most certainly to be able to control what information that Thai citizens are allowed to see, AKA North Korea, etc.
Oh, the paid version of "proXPN" ...as a VPN service, is working fine for me, btw.
have a look here, however: https://www.google.co.th/search?q=are+VPNs+illegal+in+Thailand
…and today (so far) is a "good day"... :cool2:
Good luck,
Pawpcorn -
yeah, I use 3bb.
-
Speaking as someone with over 20 years of networking experience, to me, this sounds like a routing problem on 3bb's end actually. If they're using an aggregated network, it's likely that they are using dynamic routing which would mean that depending on the time of day and network loads, they attempt to route the connection through a path that is problematic only some of the time, as is the nature of dynamic routing, which is more common to aggregated networks. I would be curious to see the traceroute as far as it will go (to Hyperfilter IIRC) on a day when it is working and a day when it is not to see the difference in the route that it tries to take. Chances are that it may not be directly on 3bb's end, but rather, something to do with blockades being put in place by one of their third party upstream vendors that provides the actual route through the internet. If this is the case, this would explain why 3bb is scratching their heads trying to figure it out, as the problem would be with the routing through only some of the network paths that they use. The sad part about dynamic routing is that depending on a number of factors, the route will change from one time of the day to the next. I suspect that the problem very well may be that they are trying to route though another country at times, which may run into blockades placed by foreign government.
The other possibility (although unlikely) is that the problem lies within the DNS servers, which do not actively respond properly as they should, although from the sounds of it, this is far less likely. Part of why I suspect that it may be the routing is based on issues that I have seen pop up with my ISP from time to time. For example, there was recently a problem with one of the routes that my ISP (TekSavvy) was using to get to YouTube. The connection would pass successfully from my modem, through their gateway, through the Toronto Internet Exchange (Packetflow I believe they refer to it as), then would bounce through Hurricane Electric's network grid. The problem came in however that when trying to send the traffic through one particular route through HE (Detroit I believe it was), the packet would make it into the first system, but then would frequently drop between the first hop in HE's system in Detroit and one of the two following relays in that route. Once TekSavvy changed the route to run through Chicago instead, the problem cleared up. The interesting part is that this problem was not limited only to YouTube, but also to other streaming sites, some of which were located in Canada. So… Even though the connection was going from Canada to Canada, at some point in the middle of the route, the connection takes a few bounces through the United States... So.... If the same kind of thing is happening with 3bb, it is possible that the problem may be with the dynamic routing trying to route requests at times through a country which has a blockade on this type of internet traffic.
It's a very high-tech explanation, but I'm almost certain that this will be the key to what the so-called "professionals" are overlooking. That is of course, assuming that they are actually being retarded and overlooking the possibility of routing through a foreign territory in some of their dynamic routes, rather than just not bothering to mention it or check for it because it's a "gay" thing, so they cannot be bothered. I don't know how vast homophobia is in that part of the world, so it's hard to say whether they're overlooking it, or they're just assuming it's not on their end because the connection leaves their network, so they cannot be bothered to look into it in more detail. Nevertheless, the traceroutes on a day when it works and on a day when it doesn't work compared to one another will surely tell whether or not this is the case. I would strongly suspect that their "technicians" are defined as the "barely trained" technicians as referred to in this video are just blindly pointing the finger at GT.ru for the problem because they're not looking past their network. They're likely only looking at the traffic as it passes through the part of the network that is their own domain, ignoring the fact that problems may arise in the routing past their network, but before the destination.
Perhaps this may provide the answer to your problem? If the routing is the case, this also explains why the connection works just fine through a VPN, as a VPN will force all of your traffic to be routed through the VPN tunnel to get out to the internet, thereby forcing it to take a route other than the one allocated by your ISP by bouncing the traffic off of the VPN instead of taking your ISP's default route.
-
Thank you for your offer to help, MrMazda… although "knowing the reality" of 3bb's problem isn't going to make them fix it, eh? Especially since they don't speak English, and pornography is technically illegal in Thailand (go figure)
ANYWAY!!! I did what you asked, and came up with the FOUR following tracert's: Looking forward to hearing your analysis.
connecting OK via 3bb:
Tracing route to www.gaytorrent.ru [185.30.166.2]
over a maximum of 30 hops:1 244 ms 246 ms 244 ms 192.168.26.1
2 257 ms 254 ms 247 ms 1-52-209-178.static.edis.at [178.209.52.1]
3 263 ms 263 ms 262 ms e1-6.c-r1.cz41.nine.ch [5.148.160.118]
4 245 ms 245 ms * e1-1.c-r1.cz42.nine.ch [5.148.160.101]
5 246 ms 246 ms 246 ms te0-0-1-3.nr11.b021036-0.zrh01.atlas.cogentco.co
m [149.6.177.225]
6 250 ms 245 ms 245 ms te0-0-2-3.agr11.zrh01.atlas.cogentco.com [154.25.3.13]
7 246 ms 246 ms 245 ms te0-0-0-35.ccr21.zrh01.atlas.cogentco.com [154.54.57.165]
8 254 ms 251 ms 251 ms be2023.ccr21.muc03.atlas.cogentco.com [130.117.0.249]
9 257 ms 256 ms 257 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
10 262 ms 262 ms 265 ms be2813.ccr41.ams03.atlas.cogentco.com [130.117.0.121]
11 264 ms 264 ms 266 ms be2519.rcr21.b015960-1.ams03.atlas.cogentco.com[130.117.3.98]
12 269 ms 261 ms 261 ms 149.14.82.146
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.later on, NOT connecting via 3bb:
Tracing route to www.gaytorrent.ru [185.30.166.2]
over a maximum of 30 hops:1 1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 25 ms 92 ms 10.121.41.217
3 26 ms 25 ms 25 ms 10.121.41.226
4 46 ms 35 ms 35 ms mx-ll-110.164.0-139.static.3bb.co.th [110.164.0.139]
5 34 ms 34 ms 34 ms mx-ll-110.164.0-138.static.3bb.co.th [110.164.0.138]
6 34 ms 33 ms 33 ms mx-ll-110.164.1-13.static.3bb.co.th [110.164.1.13]
7 34 ms 34 ms 34 ms mx-ll-110.164.1-117.static.3bb.co.th [110.164.1.117]
8 34 ms 37 ms 33 ms mx-ll-110.164.1-6.static.3bb.co.th [110.164.1.6]9 226 ms 226 ms 226 ms 192.168.255.250
10 239 ms 248 ms 250 ms ams-ix.rtr1.az16.z1.gsa.nforce.nl [80.249.210.175]
11 241 ms 243 ms 310 ms 185.107.116.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * ^Cconnecting OK (altho trying to access my profile AND the forum… hung..... via VPN (Zurich)
Tracing route to www.gaytorrent.ru [185.30.166.2]
over a maximum of 30 hops:1 240 ms 240 ms 240 ms 192.168.26.1
2 240 ms 241 ms 242 ms 1-52-209-178.static.edis.at [178.209.52.1]
3 269 ms 247 ms 278 ms e1-6.c-r1.cz41.nine.ch [5.148.160.118]
4 * 247 ms 250 ms e1-1.c-r1.cz42.nine.ch [5.148.160.101]
5 242 ms 240 ms 241 ms te0-0-1-3.nr11.b021036-0.zrh01.atlas.cogentco.com [149.6.177.225]
6 244 ms 244 ms 241 ms te0-0-2-3.agr11.zrh01.atlas.cogentco.com [154.25.3.13]
7 241 ms 241 ms 241 ms te0-0-0-35.ccr21.zrh01.atlas.cogentco.com [154.54.57.165]
8 247 ms 247 ms 246 ms be2023.ccr21.muc03.atlas.cogentco.com [130.117.0.249]
9 251 ms 252 ms 253 ms be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
10 260 ms 259 ms 259 ms be2813.ccr41.ams03.atlas.cogentco.com [130.117.0.121]
11 261 ms 268 ms 261 ms be2519.rcr21.b015960-1.ams03.atlas.cogentco.com[130.117.3.98]
12 258 ms 330 ms 257 ms 149.14.82.146
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 ^C=====================================================================
Connecting to GTRU with Profile and Forum access OK! via VPN (Netherlands)Tracing route to www.gaytorrent.ru [185.30.166.2]
over a maximum of 30 hops:1 * 251 ms 251 ms 192.168.41.1
2 254 ms 438 ms 261 ms 213.179.208.129
3 254 ms 254 ms 253 ms 109.200.218.246
4 255 ms 254 ms 265 ms nforce.globalswitch.nl-ix.net [193.239.116.142]
5 254 ms 268 ms 262 ms 185.107.116.2
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.Take care,
Pawpcorn -
Exactly as I suspected…. When the route goes through Switzerland to China, then it bounces through the United States, the connection works just fine...
When the route tries to run through the 3bb platform most of the way, it seems it chokes.... This confirms what I suspected, and actually makes me think that the technician doesn't know what they're doing :lolp:
What I find interesting is this part of the one traceroute where it does not work
8 34 ms 37 ms 33 ms mx-ll-110.164.1-6.static.3bb.co.th [110.164.1.6]
9 226 ms 226 ms 226 ms 192.168.255.250The interesting part is to see if the internal LAN IP that you're reaching where the ping suddenly spikes is on 3bb's end, or if this is an obscure private link between 3bb and nForce that isn't working correctly. Based on the sudden spike in the ping between the two, I'm willing to put money down that says that this is where the connection drops when it fails. If this internal hop is between 3bb and nForce, this may explain why 3bb is saying that the problem is with GT.ru because they're only looking at the packets as they pass through the 3bb network. This definitely does confirm my theory that it's an aggregated network that uses dynamic routing. If they were smart, what they would do is to pull the dynamic route that runs primarily through their platform, since there's obviously a disconnect somewhere between 3bb and nForce when they route traffic this way.
So… It's possible that the packet leaves the 3bb network successfully, but chokes between 3bb and nForce, in which case it would only make sense that 3bb is scratching their heads, because they're completely overlooking a major routing issue. The internal 192.168.x.x IP address is also of some concern as generally speaking, you're not supposed to have private network addresses along a route, unless the route is accessible through your network directly. This is to ensure that you're able to successfully ping and route through that gateway, which leads me to believe that the problem is in fact within 3bb's network, namely in one of their exit nodes that passes traffic out to one of their internet exchanges. If this is the case, then the problem is on 3bb's end because it's one of their own internal exit nodes that is failing. This will no doubt create major routing issues for more than just GT.ru. Come to think of it, it's likely that this internal link is indeed a 3bb link, in which case they're just full of shit and don't want to fix their own platform. I know that latency will vary slightly from one hop to the next, but with a difference in latency like that (spiking from 34 to 226 ms) is generally an indication that either there is a hardware issue with the link, or that said link may be over-saturated with network traffic, in which case, their load balancing is not properly configured.
I'd be inclined to start asking questions about that route myself as the sudden spike in latency is definitely something that shouldn't be happening. Since the problem seems to be with one of the dynamic routes that they're taking, this would explain why a VPN makes it work, as this forces traffic to take a different route, thus bypassing the particular gateway (or node) in the 3bb network that links into the internet exchange to hop over from Thailand to the Netherlands. While the traceroute may be able to make its way through to nForce, I kind of wonder if the larger packets such as would be used for HTTP traffic are too large to be able to pass through, due to whatever is causing the latency to spike at that point in the connection. The other thing that I find interesting is that on two separate routes, there's a ping timeout when the connection routes through China, which leads me to believe that there may be an intermittent problem on that end of the platform when it runs through the Nine network. One thing that I can say for sure though is that there is definitely dynamic routing in place here, which explains why it works sometimes with 3bb, but not others, depending on whether or not it takes the route through the faulty link at the end of 3bb's platform.
-
Well thank you SO MUCH!!!!
My Thai friend is going to TRY to relay your information to 3bb… tomorrow.
MUCH APPRECIATED!!!!
Kinda confirms what I suspected, but I didn't have the proper technical vocabulary to even begin to verbalize it...
Thanks again,
Pawpcorn -
As a personal update…
I switched to TOT fiber 2 weeks ago... without a single hitch.
For nearly the same price as I was paying to 3bb, I now have 3 times faster uploading speed, and 4 times faster downloading speed, with NEVER a day where THIS site, and the other gay torrent sites are not connectable.
Summary, 3bb is a huge unreliable rip-off, which charged me a huge fine for breaking the supposed 1-year "contract" 6 months in, even tho I supported the REPORTED, yet UNRESOLVED connection issues with numerous printouts and screen dumps, and returned their hardware in perfect condition.
Avoid 3bb at all costs!
Hugs,
Pawpcorn
