Tot Is Blocking Forum.Vuze.Com

[JetsetBkk]

Anyone else able to get to here: http://forum.vuze.com/index.jspa

I haven't been able to for the last 3 or 4 days, unless I switch on that smelly onion thingy that we're not allowed to talk about.

So a forum about a software product that enables downloading of torrents is now blocked? Where will it all end?

[Supernova]

Can access site, no problems.

[sulasno]

what smelly onion ? it'a rot onion lol

[Sunny Valentine]

The "smelly onion" thingy is your friend, when it comes to overcome the inefficiency and blatant ignorance of the law by your ISP.

Remember, and have a look at the Thai Visa rules: It is forbidden to discuss Proxies and the like as a means to bypass legal blockages. These blockages must be confirmed by a court in Thailand. Lots of pages, including wikileaks, seem to be blocked, but only by either the ISPs own illegal decisions, or most likely by their incompetence.

So far, neither vuze.com nor wikileaks.com are known to be blocked by a court decision, so I reckon using Tor or other means to bypass glitches of the internet or illegal censorship by local ISPs are perfectly ok.

Edited August 25, 2010 by Sunny Valentine

[gotlost]

Ok for me. Get another ISP

[Cloggie]

No problems with this site - use TOT / Banglamung

[kevjohn]

No problems with TOT for me.

I'm in Korat

[lomatopo]

Works on TOT, TRUE and CSLoxInfo.

It's just you. http://forum.vuze.com is up.

Check another site?

[JetsetBkk]

Can access site, no problems.

I presume you are on TOT? Very strange.

[JetsetBkk]

what smelly onion ? it'a rot onion lol

Correct!

The "smelly onion" thingy is your friend, when it comes to overcome the inefficiency and blatant ignorance of the law by your ISP.

Remember, and have a look at the Thai Visa rules: It is forbidden to discuss Proxies and the like as a means to bypass legal blockages. These blockages must be confirmed by a court in Thailand. Lots of pages, including wikileaks, seem to be blocked, but only by either the ISPs own illegal decisions, or most likely by their incompetence.

So far, neither vuze.com nor wikileaks.com are known to be blocked by a court decision, so I reckon using Tor or other means to bypass glitches of the internet or illegal censorship by local ISPs are perfectly ok.

OK, so yes, I can get there using TOR but when I turn it off, my Firefox displays the usual timeout message. It is 100% consistent - with TOR: access OK, without TOT: no access...

With TOR:

Without TOR:

[JetsetBkk]

Works on TOT, TRUE and CSLoxInfo.

It's just you. http://forum.vuze.com is up.

Check another site?

OK thanks, tried that and the site says it is just me.

But when I click on that link to forum.Vuze on their web page, I get the timeout message. What can be doing this?

A zillion bonus points to whoever can suss this out!

[JetsetBkk]

I just searched my 'Hosts' file in \windows\system32\drivers\etc - nothing about "Vuze".

[JetsetBkk]

"PingPlotter freeware" says destination address unreachable.

OK, 2 zillion bonus points...

[JetsetBkk]

IE:

"Internet Explorer cannot display the web page"

Where's the "pulling hair out" smiley?"

[Supernova]

I presume you are on TOT? Very strange.

I'm with JI-NET.

Without TOR:

Looks to be a routing issue. Try changing DNS servers.

[JetsetBkk]

The link is

http://forum.vuze.com/index.jspa

So what's this index.jspa?

I haven't seen many .jspa's before.

[JetsetBkk]

<snip>

Looks to be a routing issue. Try changing DNS servers.

Yes, did that already. From TOT's DNS server to Google's - 8.8.8.8/8.8.4.4. Same problem. Very weird.

[lomatopo]

Do a tracert, post the results.

[JetsetBkk]

Do a tracert, post the results.

Not good:

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:

-d Do not resolve addresses to hostnames.

-h maximum_hops Maximum number of hops to search for target.

-j host-list Loose source route along host-list.

-w timeout Wait timeout milliseconds for each reply.

C:\Documents and Settings\user>tracert forum.vuze.com

Tracing route to ec2-174-129-43-34.compute-1.amazonaws.com [174.129.43.34]

over a maximum of 30 hops:

1 Destination host unreachable.

Trace complete.

C:\Documents and Settings\user>

Also, "ping" results in "Destination host unreachable."

C:\Documents and Settings\user>ping forum.vuze.com

Pinging ec2-174-129-43-34.compute-1.amazonaws.com [174.129.43.34] with 32 bytes of data:

Destination host unreachable.

Destination host unreachable.

Destination host unreachable.

Destination host unreachable.

Ping statistics for 174.129.43.34:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\user>

[JetsetBkk]

<snip>

Looks to be a routing issue. Try changing DNS servers.

Yes, did that already. From TOT's DNS server to Google's - 8.8.8.8/8.8.4.4. Same problem. Very weird.

Also tried OpenDNS. Same result.

Also deleted everything from my Hosts file except

127.0.0.1 localhost

127.0.0.1 w3.mict.co.th

and rebooted. Same result.

[JetsetBkk]

OK, found it.

"Peerblock" - the program to protect Vuze from nasty IPs - was also blocking forum.vuze.com.

Does that make sense?

Not to me it doesn't. Anyway, I've told Peerblock not to block it and all is OK.

[lomatopo]

Tracert indicates a problem on your, (in your home) network, maybe a DNS issue, maybe a firewall issue. almost certainly operator error vs. conspiracy.

Tracert the IP address.

Edited August 26, 2010 by lomatopo

[JetsetBkk]

Tracert indicates a problem on your, (in your home) network, maybe a DNS issue, maybe a firewall issue. almost certainly operator error vs. conspiracy.

Tracert the IP address.

Yep, did that too.

But see the post above yours. All is explained!