Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

Downtime Connection closed by peer, BT

views
     
YiQi
post Jan 17 2007, 05:35 PM

Getting Started
**
Junior Member
164 posts

Joined: Jan 2003
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
YiQi
post Jan 18 2007, 01:59 PM

Getting Started
**
Junior Member
164 posts

Joined: Jan 2003
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
YiQi
post Jan 18 2007, 04:31 PM

Getting Started
**
Junior Member
164 posts

Joined: Jan 2003
If ping to local IP is suffering high latency, there must be something wrong with the TMNut's router.
I did encounter strange problem, status in modem show connected, but ping gateway even get timeout, have to DC and connect again.

Pinging to www.tm.net.my here (my office) looks okie, avg 30ms.

Guys, are you pinging any site when using P2P at the same time?
If yes, you will suffering slow response when too many connection at you modem/router, even pinging your gateway.

To get accurate statistic, don't run any P2P program, if you just close it, wait for about 10 minutes to let your connection closed properly, completely.

If you use cFosSpeed, try toggle the 'Favour Ping Time'.
YiQi
post Jan 18 2007, 05:33 PM

Getting Started
**
Junior Member
164 posts

Joined: Jan 2003
Well, something to figure out where is the bottleneck, traceroute (tracert) maybe useful. I found quite a lots of time the bottleneck is the gateway itself. e.g.

My traceroute from my office:
traceroute to www.lowyat.net (202.190.197.144), 30 hops max, 38 byte packets
1 60.xx.xx.xx (60.xx.xx.xx) 0.646 ms 0.592 ms 0.525 ms
2 219.93.218.176 (219.93.218.176) 43.576 ms 23.214 ms 9.311 ms
3 219.93.216.225 (219.93.216.225) 4.362 ms 4.334 ms 5.092 ms
4 210.187.143.1 (210.187.143.1) 4.467 ms 4.309 ms 4.072 ms
5 219.93.182.232 (219.93.182.232) 5.064 ms 4.279 ms 4.371 ms
6 202.71.100.9 (202.71.100.9) 4.359 ms 4.583 ms 4.349 ms
7 202.75.52.3 (202.75.52.3) 4.643 ms 4.570 ms 4.363 ms
8 218.100.22.243 (218.100.22.243) 4.659 ms 4.555 ms 4.646 ms
9 218.100.22.34 (218.100.22.34) 5.189 ms 5.885 ms 7.429 ms
10 ge3-0.jsr4.jaring.my (161.142.173.10) 4.904 ms 5.389 ms 5.445 ms
11 * * *
12 * * *

ignore the 11, 12.. and further, probably traceroute ICMP is blocked there.
Usually, try to ping your gateway first, in my example, the No.2.
Occasionally, I found huge delay at the gateway, especially when my line is in high utilization, when some peoples download heavy stuff (software patches, movie trailers....), until their download finish, the ping time drop to normal. This is my experience.


Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0179sec    0.63    7 queries    GZIP Disabled
Time is now: 4th December 2025 - 04:51 PM