Tracker connection issue

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
jnicol
Posts: 10
Joined: Mon Jun 05, 2006 11:06 am

Re: Tracker connection issue

Post by jnicol » Sun Jul 20, 2008 4:35 pm

Yep, just adding my voice to the chorus. I'm pleased I found this thread, I've been messing around with utorrent, my firewall etc. At least know I know Exetel is at fault...

Twisted
Posts: 5
Joined: Sun Jul 20, 2008 12:58 pm
Location: NSW

Re: Tracker connection issue

Post by Twisted » Sun Jul 20, 2008 5:23 pm

Use a BT client that's capable of using a proxy server (uTorrent can)
Find and test a proxy server from this list: http://www.samair.ru/proxy/type-01.htm
They don't all work but I've found one that does. Use that until this issue is sorted out.

Mussels
Posts: 16
Joined: Wed Jun 04, 2008 1:03 pm
Location: Victoria

Re: Tracker connection issue

Post by Mussels » Sun Jul 20, 2008 5:47 pm

Twisted wrote:Use a BT client that's capable of using a proxy server (uTorrent can)
Find and test a proxy server from this list: http://www.samair.ru/proxy/type-01.htm
They don't all work but I've found one that does. Use that until this issue is sorted out.

thank you very much man, for that workaround.

edit: first one in the list lets me connect to a few, so it works well enough.

Exetel: come on, fix this. i know its a sunday, but you gotta have at least one technician there on weekends who can hit the reset button.

Mussels
Posts: 16
Joined: Wed Jun 04, 2008 1:03 pm
Location: Victoria

Re: Tracker connection issue

Post by Mussels » Mon Jul 21, 2008 12:03 am

just as an update: i can connect to a few private trackers no problems and get good speeds, but even using the proxy trick for the public ones i'm getting stuck around 20KB/s

Peter S
Posts: 7
Joined: Sun Nov 04, 2007 10:51 pm
Location: Jindera

Re: Tracker connection issue

Post by Peter S » Mon Jul 21, 2008 10:39 am

It's happening for ADSL customers too through Exetel and yet nobody (as in forum admins or moderators) are at least even posting about this to give us some form of a heads up.

Mussels
Posts: 16
Joined: Wed Jun 04, 2008 1:03 pm
Location: Victoria

Re: Tracker connection issue

Post by Mussels » Mon Jul 21, 2008 3:19 pm

Peter S wrote:It's happening for ADSL customers too through Exetel and yet nobody (as in forum admins or moderators) are at least even posting about this to give us some form of a heads up.
i submitted a fault and basically got told 'we dont block P2P! its just their nature that P2P trackers will go offline!'

i then linked exetel to this thread. seriously, it cant be that hard to admit theres a problem can it?

RichS
Posts: 22
Joined: Tue Jun 27, 2006 8:42 am
Location: Sydney, Northern Beaches

Re: Tracker connection issue

Post by RichS » Mon Jul 21, 2008 3:53 pm

Blocked or not the traffic does not appear to leave Exetel network.

From Exetel connection:

C:\Documents and Settings\rsawkins>tracert vip.tracker.thepiratebay.org

Tracing route to vip.tracker.thepiratebay.org [77.247.176.154]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms XXXXXXXXXXXXXXXXXX
2 * * * Request timed out.
3 33 ms 26 ms 27 ms 254.0.233.220.exetel.com.au [220.233.0.254]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

From Telstra :

C:\Documents and Settings\rsawkins>tracert vip.tracker.thepiratebay.org

Tracing route to vip.tracker.thepiratebay.org [77.247.176.154]
over a maximum of 30 hops:

1 3 ms 1 ms 2 ms xxxxxxxxxxxxxxxx
2 3 ms 2 ms 3 ms xxxxxxxxxxxxxx
3 18 ms 11 ms 12 ms Serial2-2.chw24.telstra.net [139.130.142.193]
4 20 ms 12 ms 14 ms TenGigE0-1-0-0.chw-core2.Sydney.telstra.net [203.50.20.129]
5 16 ms 12 ms 12 ms Bundle-Ether1.oxf-gw2.Sydney.telstra.net [203.50.6.90]
6 13 ms 14 ms 14 ms TenGigabitEthernet14-0.sydo-core01.Sydney.reach.com [203.50.13.42]
7 13 ms 16 ms 35 ms i-10-0.syd-core03.net.reach.com [202.84.221.85]
8 21 ms 15 ms 14 ms i-4-2.sydp-core01.net.reach.com [202.84.249.13]
9 173 ms 161 ms 160 ms i-3-0.wil-core03.net.reach.com [202.84.140.29]
10 163 ms 162 ms 172 ms i-3-4.tlot03.net.reach.com [202.84.251.162]
11 * * * Request timed out.
12 292 ms 297 ms 203 ms 10gigabitethernet1-2.core1.dal1.he.net [72.52.92.58]
13 314 ms 306 ms 304 ms 10gigabitethernet5-2.core1.ash1.he.net [72.52.92.62]
14 413 ms 326 ms 374 ms 10gigabitethernet1-2.core1.ams1.he.net [72.52.92.98]
15 * * * Request timed out.
16 433 ms 410 ms 409 ms 10ge-v3.core-1.ipv6-mg8.db-ams.euroaccess.nl [85.12.0.33]
17 406 ms 406 ms 412 ms 10GE.Nforce.ams.euroaccess.nl [193.138.220.82]
18 * 435 ms 409 ms 77.247.176.173
19 441 ms 402 ms 411 ms 77.247.176.154

ez2
Posts: 8
Joined: Sat Jul 19, 2008 12:38 pm
Location: Hobart

Re: Tracker connection issue

Post by ez2 » Mon Jul 21, 2008 3:59 pm

Do a ping of your tracker, bet you get no results - non-definitive result tho - it doesnt mean the tracker is NOT reachable, could also mean its down .
Do a traceroute (tracert for winblows) notice the route dies inside exetel's network.
Now go to www.iptools.com and do it all again - if you get ping results and traceroute succeeds, the server/host is a live and exetel's network is broken.
STILL!!

I really wish an exetel rep would post here and let us know what the hells going on - I logged a call last monday and rang back again later in the week.

customer service is - um "slipping" ..


Ez

Matt
Posts: 5
Joined: Fri Sep 15, 2006 6:30 pm

Re: Tracker connection issue

Post by Matt » Mon Jul 21, 2008 4:01 pm

I am also having this problem with the same listed trackers as above.

DylanF
Exetel Staff
Posts: 200
Joined: Tue Sep 13, 2005 2:28 pm
Location: Sydney

Re: Tracker connection issue

Post by DylanF » Mon Jul 21, 2008 4:52 pm

I have asked someone to look in to this for you.

Mussels
Posts: 16
Joined: Wed Jun 04, 2008 1:03 pm
Location: Victoria

Re: Tracker connection issue

Post by Mussels » Mon Jul 21, 2008 10:34 pm

DylanF wrote:I have asked someone to look in to this for you.
Thank you Dylan.
while i was it was dealt with sooner, i am glad that you are getting it looked at now.

update: as of 11PM, monday 21st july the problem still exists. using a proxy solves the problem, but doesnt offer any real solution as the speeds are still terrible.

ez2
Posts: 8
Joined: Sat Jul 19, 2008 12:38 pm
Location: Hobart

Re: Tracker connection issue

Post by ez2 » Tue Jul 22, 2008 8:15 am

Been going through some of the reported trackers with interesting results.

firstly it looks as though tracker.zerotracker.com is bogus - it resolves to localhost (127.0.0.1)

here's a ping log for all the ones posted here - there is a pattern (I already knew that).
I also notice that I can ping *some* of the trackers - which may indicate that they are not the ones that are not resolving.
I would suggest that these trackers actually had a problem or timed out from peoples clients.
The ones that seem to (reliably) fail <-- Aint that a mouthfull! are all within the same address range.
Pretty much anything that resolves to 77.247.176.0/20 fails, which includes all of TPB and many others.

I've compared all my results with the same efforts at www.iptools.com, which successfully
completed pings and traceroutes for *almost* all of the list

files is plaintext contents are :
eztv.ukrabel.com
eztv.sladinki007.net
tracker1.istole.it
tracker2.istole.it
tracker3.istole.it
tracker4.istole.it
tv.tracker.prq.to
tracker.prq.to
tracker.thepiratebay.org
vip.tracker.thepiratebay.org
tpb.tracker.thepiratebay.org
open.tracker.thepiratebay.org
www.torrent-downloads.to
denis.stalker.h3q.com
tracker.zerotracker.com
eztv.sladinki007.eu
tracker.sladinki007.net
tracker.sladinki007.net
tv.sladinki007.net
tv.tracker.thepiratebay.org
eztv.tracker.thepiratebay.org

output from:

( have done tests with -c unset and set to larger numbers - I set c to 5 just to keep the results indicative for this message )

for f in $(cat files); do ping -c 5 $f ; done

PING eztv.ukrabel.com (208.67.219.132) 56(84) bytes of data.
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=1 ttl=52 time=205 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=2 ttl=52 time=208 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=3 ttl=52 time=203 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=4 ttl=52 time=220 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=5 ttl=52 time=204 ms

--- eztv.ukrabel.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 203.763/208.511/220.384/6.173 ms
PING eztv.sladinki007.net (91.121.103.182) 56(84) bytes of data.
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=1 ttl=48 time=357 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=2 ttl=48 time=400 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=3 ttl=48 time=344 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=4 ttl=48 time=415 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=5 ttl=48 time=360 ms

--- eztv.sladinki007.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 344.476/375.610/415.702/27.452 ms
PING tracker1.istole.it (24.213.90.97) 56(84) bytes of data.

--- tracker1.istole.it ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4009ms

PING tracker2.istole.it (24.213.90.97) 56(84) bytes of data.

--- tracker2.istole.it ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4001ms

PING tracker3.istole.it (24.213.90.97) 56(84) bytes of data.

--- tracker3.istole.it ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4002ms

PING tracker4.istole.it (24.213.90.97) 56(84) bytes of data.

--- tracker4.istole.it ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

PING tv.tracker.prq.to (77.247.176.154) 56(84) bytes of data.

--- tv.tracker.prq.to ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

PING tracker.prq.to (77.247.176.136) 56(84) bytes of data.

--- tracker.prq.to ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4001ms

PING tracker.thepiratebay.org (77.247.176.134) 56(84) bytes of data.

--- tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

PING vip.tracker.thepiratebay.org (77.247.176.154) 56(84) bytes of data.

--- vip.tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4008ms

PING tpb.tracker.thepiratebay.org (77.247.176.151) 56(84) bytes of data.

--- tpb.tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms

PING open.tracker.thepiratebay.org (77.247.176.134) 56(84) bytes of data.

--- open.tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

PING torrent-downloads.to (92.241.164.21) 56(84) bytes of data.
64 bytes from 92.241.164.21: icmp_seq=1 ttl=49 time=402 ms
64 bytes from 92.241.164.21: icmp_seq=2 ttl=49 time=410 ms
64 bytes from 92.241.164.21: icmp_seq=3 ttl=49 time=393 ms
64 bytes from 92.241.164.21: icmp_seq=4 ttl=49 time=434 ms

--- torrent-downloads.to ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4010ms
rtt min/avg/max/mdev = 393.577/410.432/434.634/15.213 ms
PING denis.stalker.h3q.com (77.247.176.153) 56(84) bytes of data.

--- denis.stalker.h3q.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4001ms

PING tracker.zerotracker.com (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.074 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.052 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.049 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=4 ttl=64 time=0.067 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=5 ttl=64 time=0.043 ms

--- tracker.zerotracker.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.043/0.057/0.074/0.011 ms
PING eztv.sladinki007.eu (91.121.103.182) 56(84) bytes of data.
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=1 ttl=48 time=416 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=2 ttl=48 time=344 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=3 ttl=48 time=344 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=4 ttl=48 time=343 ms
64 bytes from fluffybunnies.servebeer.com (91.121.103.182): icmp_seq=5 ttl=48 time=343 ms

--- eztv.sladinki007.eu ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 343.528/358.511/416.129/28.820 ms
PING tracker.sladinki007.net (208.67.219.132) 56(84) bytes of data.
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=1 ttl=52 time=297 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=2 ttl=52 time=312 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=3 ttl=52 time=242 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=4 ttl=52 time=307 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=5 ttl=52 time=205 ms

--- tracker.sladinki007.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4016ms
rtt min/avg/max/mdev = 205.671/273.116/312.306/41.876 ms
PING tracker.sladinki007.net (208.67.219.132) 56(84) bytes of data.
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=1 ttl=52 time=210 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=2 ttl=52 time=205 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=3 ttl=52 time=205 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=4 ttl=52 time=204 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=5 ttl=52 time=205 ms

--- tracker.sladinki007.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4010ms
rtt min/avg/max/mdev = 204.176/206.024/210.481/2.279 ms
PING tv.sladinki007.net (208.67.219.132) 56(84) bytes of data.
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=1 ttl=52 time=203 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=2 ttl=52 time=290 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=3 ttl=52 time=304 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=4 ttl=52 time=203 ms
64 bytes from hit-nxdomain.opendns.com (208.67.219.132): icmp_seq=5 ttl=52 time=212 ms

--- tv.sladinki007.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 203.645/242.982/304.614/44.998 ms
PING tv.tracker.thepiratebay.org (77.247.176.154) 56(84) bytes of data.

--- tv.tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4009ms

PING eztv.tracker.thepiratebay.org (77.247.176.154) 56(84) bytes of data.

--- eztv.tracker.thepiratebay.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms


I wont post all the traceroute logs just this one as its typical of the results for the ones we cant ping.
traceroute eztv.tracker.thepiratebay.org
traceroute to eztv.tracker.thepiratebay.org (77.247.176.154), 30 hops max, 40 byte packets
1 29.244.233.220.exetel.com.au (220.233.244.29) 1.797 ms 1.755 ms 1.698 ms
2 121.1.233.220.exetel.com.au (220.233.1.121) 39.586 ms 161.458 ms 71.291 ms
3 252.0.233.220.exetel.com.au (220.233.0.252) 146.026 ms 43.062 ms 41.081 ms
4 * * *

VK
Posts: 21
Joined: Fri May 13, 2005 10:38 pm

Re: Tracker connection issue

Post by VK » Tue Jul 22, 2008 9:35 am

I think this is definitely an issue with Exetel. I am at another location with ADSL provided by internode and I ssh to my home server hooked to Exetel (ADSL2 in Adelaide). From the Internode place:

wget http://tpb.tracker.thepiratebay.org/announce -O -
--08:47:33-- http://tpb.tracker.thepiratebay.org/announce
=> `-'
Resolving tpb.tracker.thepiratebay.org... done.
Connecting to tpb.tracker.thepiratebay.org[77.247.176.151]:80... connected.
HTTP request sent, awaiting response... 400 Invalid Request
08:47:37 ERROR 400: Invalid Request.

(i.e. we have a connection and the server is returning an error - as expected)

From my home server:
wget http://tpb.tracker.thepiratebay.org/announce -O -
--08:49:29-- http://tpb.tracker.thepiratebay.org/announce
=> `-'
Resolving tpb.tracker.thepiratebay.org... 77.247.176.151
Connecting to tpb.tracker.thepiratebay.org|77.247.176.151|:80... failed: Connection timed out.
Retrying.

--08:52:39-- http://tpb.tracker.thepiratebay.org/announce
(try: 2) => `-'
Connecting to tpb.tracker.thepiratebay.org|77.247.176.151|:80... failed: Connection timed out.
Retrying.

(and so on...)

Both tests were executed at the same time, therefore server tpb.tracker.thepiratebay.org was definitely on at the time.

Please fix it.

ez2
Posts: 8
Joined: Sat Jul 19, 2008 12:38 pm
Location: Hobart

Re: Tracker connection issue

Post by ez2 » Tue Jul 22, 2008 9:56 am

The failure to be able to connect to a tracker has almost no bearing on the speed of downloads.
A tracker only gives your client the information it needs in order to connect to peers/seeds.

This excerpt is from the vanilla bittorrent tracker scrape extension protocol - it may help to clear up what is going on
There are two intervals, the announce - which informs tracker of the
status of things, and the rerequest which is based on whether the peer
has a connection and/or has it's peer list fulfilled. Currently, the
tracker doesn't set a min reqrequest interval (though it could); the
tracker only sets a default announce interval. Thus, peers by default
request peers (thus announcing) every 5 mins until they fulfill their
peers list and then resort to announcing every 30 minutes. This is only
how the source client works, I'm not sure how the others do but I'm
sure they are similar.

By default, the announce request is 5 mins or 30, depending on how many
peers the client has and if it's been connected to. The majority of
swarms won't maintain a full peer list and will average closer to the 5
min interval than the 30 min interval (excepting torrents with peer
counts disproportional to the content's size).
Original text here :http://lists.ibiblio.org/pipermail/bitt ... 01114.html

Announce interval is something clients adhere to very poorly,
if a tracker gets saturated with announce's its gonna get slow to respond
same with rerequest interval <- this one is often configurable in the client.
so for trackers you CAN ping, dont bog them down with announce and rerequest, get enough seeds to get a decent speed.

Hopefully this clears up the fact that torrents being slow is not really related to the issue of clients being unable to connect to a tracker
OTHER THAN the case where your client did at one time connect to a tracker and get peers, then the tracker became unreachable, and after a while the
peers and seeds have gone away and your client has only a few left and cant get any more because it cant connect to a tracker.

Throughout the time this problem has existed I've still managed to complete ALL my downloads by getting the torrent hash and chucking it in google or isohunt and finding a tracker to which I CAN connect to.

To the folks at exetel: I would like NOT to have to do this for every damn torrent!


In the bittorrent world, "The long wait for a download to complete is directly proportional to greed and patience"

JingW
Posts: 70
Joined: Wed Sep 19, 2007 3:40 pm

Re: Tracker connection issue

Post by JingW » Tue Jul 22, 2008 11:34 am

Changes have been made.

thepiratebay.org should be working now.

Post Reply