All trackers from various site gives message "connection closed by peer" on my bt client since yesterday and no bt at all from my place (Bt Caves). I didn't change any setup on my client nor modem neither. Any one got this problem?



This post has been edited by payebudu: Jan 17 2007, 12:19 PM

Same here. I'm using uTorrent 1.6.1.

Maybe TMNet is starting to block p2p completely?

Thread somewhat related:

http://forum.utorrent.com/viewtopic.php?id=17547

I have the same problem. Happened to me Tuesday morning around 3am. All of a sudden, ALL trackers give the "connection closed by peer" error.

I'm using uTorrent, but tested with Azureus and the original Bittorrent, both same problem. I even changed computers, changed modem, changed different IPs, changed lines (I have 2 streamyx account/phone line here), and still the same problem. I "borrowed" my friend's account, still doesn't work.

I tested it on my friend's connection, it works fine. Weird. I think tmnet has found the Achilles heel of torrents. I'm just curious how/where are they implementing this since it doesn't affect my friend's connection.

I have no issues with speed (I get >150KB/sec), but what good is speed without being able to connect to trackers?

The more important question is, what am I gonna say to tmnet when I file a complaint?

Yeah, when I try in other location, it's ok. Means that TMNut is tracking and blocking our account (phone port) not username.

Thanks for the replies, I'm not alone now

Not all trackers are affected, some of the trackers still work for me.
I noticed this around 3am too, and around that time all my torrents went from 2-5kBps to 40-80kBps. So they were definitely doing something.

Same here... KLCC area... Using a corporate account and tried to change to different client to no avail.

Let just hope that TmNut is tweaking those lines for repair and not block phone port like you said...

This post has been edited by shyghost: Jan 17 2007, 06:07 PM

Suspect Streamyx block it base on User-Agent (client identification).
Why I know? Test by using a very common public tracker http://tracker.prq.to/announce.

First of all, I test it in Linux using 'wget'.
1. Retrieve the tracker URL without any option.
Response OK.
2. Using 'wget', specify the User-Agent as 'uTorrent'
Got 'Connection reset by peer.' Sucks!
3. Try other User-Agent strings: Azureus, BitTorrent, Shareaza
All the same, get 'Connection reset by peer.'
4. Try some nonsense User-Agent strings: test, abc, xyz
All pass, no probelm in getting the response.
Note: Surprisingly, 'BitComet' is not blocked. Maybe BitComent didn't identify itself in User-Agent as 'BitComet'.

Conclusion: Streamyx now start blocking the HTTP connection of P2P clients base on the User-Agent.
Suggestion: Find a proxy server, which can 'rewrite' your User-Agent to a common ID, e.g. IE or Firefox's ID.... to cheat. If you cannot find, install one. I use Squid for Linux.

This post has been edited by YiQi: Jan 17 2007, 05:36 PM

Funny this is I can still download eventhough the tracker connection is closed. Could it be because of having DHT enabled?

Now I got hit by this "connection closed by peer" thingy. 3am here also! So I tested with a new torrent and download won't start because it cannot connect to tracker!

miuk, only those downloads that were already started previously (before this problem) can continue!

YiQi, from your description it seems that another type of packet shaper at work? I wonder if that accounts for those odd ping times outside of Malaysia and Singapore now...



This post has been edited by lex: Jan 18 2007, 03:45 AM

DHT still works, apparently. I have no issues with torrents that allow DHT. Brilliant speeds.

The problem is with torrents from private trackers that disables DHT.

YiQi, I can now confirmed its blocked by detecting "User Agent".

I just started another torrent, brand new. No problems, in fact connection to peers are fast. Must be the DHT.

Dude, It's start to affect more users now

may some seeder be with you

Taken from my own post here: http://forum.lowyat.net/topic/361764/+960

Now can't connect to any peers. Back to 0KB/s again. WEB BROWSING HAS ALSO SLOWED DOWN!!

Ping times now

Local ~ 1100ms!
Sinagpore ~ 1200ms!
USA & rest of the world ~ 1500ms ?!

Conclusion is they now back to their original BT throttling packet/traffic shaper again!

Explanation on yesterday night and this morning sudden speed up and slow downs from my monitoring....

The first speed up is they bypassed the packet shaper. That accounts for the incredible speedup I got yeaterday plus the back to normal ping times I had (local ~ 9ms!). They were probably testing something out then...

Then they started switching routes to another packet shaper which does not throttle encrypted torrent connections BUT capable of blocking tracker connections - probably using simple pass thru protocol inspection, and not deep packet inspection. This caused all those "connection reset by peer" errors. Ping times also jumped suddenly (local ~ 62ms!)

Then today morning, they are back the original packet shaper (which does deep packet inspection) that throttles and keeps disconnecting encrypted torrent connections. Ping times went crazily high (local ~ 900ms!!)

What say you?


Note: Cannot connect to tracker but can download + can connect to tracker but cannot download = 2 different packet shapers?

Just curious, may i know which address are you pinging? Would like to try it myself as i find my web browsing to be normal. Only BT and MIRC upside down.

Problem is now that tracker is blocked, can't get connection to Malaysian users, dl is moving at snail speed.

Normal? Not now for me...

When the packet shaper was off last nite, my browsing went super fast. Web pages loads and displays almost instantly (even with downloading in the background).

As for the pings? Take any one you can think of... Examples of local ones which I've randomly tested...

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=980ms TTL=57
Reply from 202.188.0.133: bytes=32 time=1078ms TTL=57
Reply from 202.188.0.133: bytes=32 time=965ms TTL=57
Reply from 202.188.0.133: bytes=32 time=466ms TTL=57

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 466ms, Maximum = 1078ms, Average = 872ms

Pinging lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=1034ms TTL=52
Reply from 202.190.197.144: bytes=32 time=1090ms TTL=52
Reply from 202.190.197.144: bytes=32 time=1425ms TTL=52
Reply from 202.190.197.144: bytes=32 time=729ms TTL=52

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 729ms, Maximum = 1425ms, Average = 1069ms

Pinging ahyap.com [202.75.42.56] with 32 bytes of data:

Reply from 202.75.42.56: bytes=32 time=1163ms TTL=55
Reply from 202.75.42.56: bytes=32 time=840ms TTL=55
Reply from 202.75.42.56: bytes=32 time=969ms TTL=55
Reply from 202.75.42.56: bytes=32 time=1111ms TTL=55

Ping statistics for 202.75.42.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 840ms, Maximum = 1163ms, Average = 1020ms

Average 1 second! Didn't you notice the slight delay loading these pages?

this might be a lil bit off topic ...

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user>ping www.lowyat.net

Pinging www.lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=62ms TTL=52
Reply from 202.190.197.144: bytes=32 time=51ms TTL=52
Request timed out.
Request timed out.

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 62ms, Average = 56ms

C:\Documents and Settings\user>ping www.lowyat.net

Pinging www.lowyat.net [202.190.197.144] with 32 bytes of data:

Reply from 202.190.197.144: bytes=32 time=64ms TTL=52
Reply from 202.190.197.144: bytes=32 time=84ms TTL=52
Reply from 202.190.197.144: bytes=32 time=65ms TTL=52
Reply from 202.190.197.144: bytes=32 time=54ms TTL=52

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 84ms, Average = 66ms

C:\Documents and Settings\user>ping www.ahyap.com

Pinging ahyap.com [202.75.42.56] with 32 bytes of data:

Reply from 202.75.42.56: bytes=32 time=62ms TTL=56
Reply from 202.75.42.56: bytes=32 time=60ms TTL=56
Reply from 202.75.42.56: bytes=32 time=71ms TTL=56
Reply from 202.75.42.56: bytes=32 time=101ms TTL=56

Ping statistics for 202.75.42.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 101ms, Average = 73ms

C:\Documents and Settings\user>ping www.yahoo.com

Pinging www.yahoo-ht2.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=251ms TTL=47
Reply from 209.131.36.158: bytes=32 time=253ms TTL=48
Reply from 209.131.36.158: bytes=32 time=262ms TTL=48
Reply from 209.131.36.158: bytes=32 time=261ms TTL=47

Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 262ms, Average = 256ms

C:\Documents and Settings\user>ping www.hinet.net

Pinging www.hinet.net [61.219.38.89] with 32 bytes of data:

Request timed out.
Reply from 61.219.38.89: bytes=32 time=421ms TTL=238
Reply from 61.219.38.89: bytes=32 time=416ms TTL=238
Reply from 61.219.38.89: bytes=32 time=415ms TTL=238

Ping statistics for 61.219.38.89:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 415ms, Maximum = 421ms, Average = 417ms

As for me connection i'm wondering if it's affected by packet shaper? I was up whole night doing some revision but my BT is constant at 5kbs with 3 tasks combined.

Hey people, don't panic.
We know TMNut do a lots of trick to throttle/block P2P.
So far we know:

1. Traffic shape on Peer-2-Peer network, so you download very slow, or timeout.
2. Block HTTP connection for P2P, which is mostly used by connecting to BT Tracker.
3. May block some well-known Tracker/eMule servers.
4. May block DHT / KAD or any serverless connection as well.
5. DC your line once a while (maybe 15 minutes) so that it will 'reset' your connection, give you a different IP, and your P2P client will start from 0 again. (Dirty trick)

Ping time only show how fast & how stable the remote site response to you. Even fast response doesn't mean you can connect to them without problem, there is completely different thing.

So, for the time being, we can only:
1. Enable whatever Protocl Encryption / Obfuscation, etc in your P2P client.
2. Use VPN / Proxy if possible
3. Hide your P2P User-Agent, by using Proxy, or some P2P client have the option to change, eg. BitSpirit
some eMule Mod will change your User-Agent to Firefox if Obfuscation is enabled.

This post has been edited by YiQi: Jan 18 2007, 02:00 PM

Bypass BT tracker blocking: http://forum.lowyat.net/topic/399896