|
tracker.sixxs.net down?
![[us]](/s/countries/us.gif) Carmen Sandiego on Wednesday, 17 December 2008 16:45:33
Wondering if anyone else can hit it. Appears to be down when connecting from Microsoft Teredo, but am not sure if that's by design. :-) HTTP 400.
tracker.sixxs.net down?
Your client should use IPv6, not IPv4.
Which client are you using that it is not reporting the full error message to you?
tracker.sixxs.net down?
Carmen Sandiego on Wednesday, 17 December 2008 16:59:38
I'm using µTorrent. It's listing http://tracker.ipv6.sixxs.net/announce as the tracker. It first just stated "HTTP Error 400", but now has switched to say "offline (timed out)". Under the logger tab it does show that it found an IPv6 address.
Anyways, looks like it's not your server and nothing you can control. Another guy here who has a working SIXXS tunnel (I switched to Teredo because my tunnel quit working last week and I just can't get it going again) checked and he can get there fine. I can get to ipv6.google.com, etc. I just can't get to sixxs.net over IPv6...
tracker.sixxs.net down?
Strange that it is listing that address as that is not the address that we specify in any of the torrents in the catalog. Note that this is not an 'open' tracker, only torrents listed in the catalog are served. Thus where did you get this "http://tracker.ipv6.sixxs.net/...." from as it is wrong.
Anyways, looks like it's not your server and nothing you can control.
It is a 400 error, and that is definitely something the tracker code produces, amongst others for hosts connecting with IPv4, and also for other reasons. The reason is giving in the error message. I suggest using Wireshark or a similar tool if your torrent client is unable to display it.
I switched to Teredo because my tunnel quit working last week and I just can't get it going again
Provide details, there is a nice list on the Contact page called "Reporting Problems Checklist" which might enlighten the issue.
I just can't get to sixxs.net over IPv6...
A traceroute and other such data would be very helpful here.
As you say you are getting a 400 error back you must be talking to some server somewhere.
tracker.sixxs.net down?
Carmen Sandiego on Wednesday, 17 December 2008 18:41:20
Unfortunately, my traceroutes to any sixxs.net IPv6 address just come back as all "Request timed out.".
Looks like the source of my problem is that I can only get to sixxs.net over IPv4. The tracker responds with a 400 error on IPv4 since it's only supposed to work over IPv6.
Not sure where to go from here. I can get to other IPv6 only sites on the 'net, so I know Teredo on my local machine is working. I've given up on the AYIYA/AICCU tunnel as it's just too unreliable (it works occasionally, without rhyme or reason, but doesn't work more often, probably due to me being on Windows Vista). Routing issue between Microsoft's Teredo server and sixxs.net seems unlikely, but I'm out of ideas?
tracker.sixxs.net down?
Unfortunately, my traceroutes to any sixxs.net IPv6 address just come back as all "Request timed out.".
Which exact 'sixxs.net IPv6 addresses' are you trying? and from where?
You do realize that the PoPs are located at various ISPs, thus that would mean you can't reach any of those either?
I can get to other IPv6 only sites on the 'net, so I know Teredo on my local machine is working.
Which sites are those, and how do you reach those? Traceroute output?
I've given up on the AYIYA/AICCU tunnel as it's just too unreliable (it works occasionally, without rhyme or reason, but doesn't work more often, probably due to me being on Windows Vista).
It should work like a charm. There is absolutely no reason for it to not work unless there is some kind of firewall or similar tool dropping packets.
Routing issue between Microsoft's Teredo server and sixxs.net seems unlikely,
"Microsoft's Teredo server" can't be a problem as a Teredo server is only used to build up the initial connection, and figuring out which relay to use. Now a Teredo relay can have issues of course. But without any data at all (traceroutes, configuration details etc etc etc) nobody can help you figure out what might be wrong.
but I'm out of ideas?
What about trying to go through the "Reporting Problems Checklist" ? It is not only a list for determining problems with SixXS provided tunnels but it helps in general to try and establish where something might be going wrong.
tracker.sixxs.net down?
Shadow Hawkins on Thursday, 22 January 2009 05:03:46
Maybe I can help. I had (about a day ago) successfully connected to the tracker in Azureus. Now, I'm getting "Tracker Status: Connection Error (SocetException: Unexpected end of file from server)".
Traceroutes are as follows:
[root@localhost ~]# traceroute6 tracker.sixxs.net
traceroute to tracker.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 40 byte packets
1 cl-92.dal-01.us.sixxs.net (2001:1938:80:5b::2) 157.125 ms 157.446 ms 159.444 ms
2 2001:4de0:1000:a3::2 (2001:4de0:1000:a3::2) 159.860 ms 160.289 ms 161.001 ms
3 2001:4de0:1000:a3::2 (2001:4de0:1000:a3::2) 161.378 ms 163.188 ms 164.551 ms
[root@W2K3-1 ~]# traceroute tracker.sixxs.net
traceroute to tracker.sixxs.net (193.109.122.244), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.238 ms 0.339 ms 0.381 ms
2 * * *
3 bgp1.ij.net (207.22.166.14) 29.004 ms 30.070 ms 30.650 ms
4 66-194-206-113.static.twtelecom.net (66.194.206.113) 36.816 ms 37.164 ms 37.364 ms
5 peer-01-so-0-0-0-0.atln.twtelecom.net (66.192.243.47) 55.913 ms 55.978 ms 56.109 ms
6 64.132.69.150 (64.132.69.150) 57.276 ms 64.132.69.154 (64.132.69.154) 58.230 ms 59.671 ms
7 po15-0.core01.atl01.atlas.cogentco.com (154.54.5.109) 61.460 ms 62.380 ms 63.780 ms
8 te3-3.ccr01.atl01.atlas.cogentco.com (154.54.5.38) 66.134 ms 84.910 ms 44.675 ms
9 te8-4.ccr01.dca01.atlas.cogentco.com (154.54.24.9) 73.790 ms 74.939 ms 76.589 ms
10 te7-8.ccr02.jfk02.atlas.cogentco.com (154.54.1.234) 83.341 ms te3-4.ccr02.jfk02.atlas.cogentco.com (154.54.26.186) 86.412 ms te8-3.ccr02.jfk02.atlas.cogentco.com (154.54.26.5) 86.572 ms
11 te2-2.ccr02.bos01.atlas.cogentco.com (154.54.5.242) 184.292 ms 185.607 ms 187.072 ms
12 te9-2.mpd01.ymq02.atlas.cogentco.com (154.54.7.26) 190.660 ms 191.634 ms 192.419 ms
13 te8-2.ccr01.ams03.atlas.cogentco.com (154.54.0.69) 187.145 ms 190.602 ms 191.636 ms
14 vl3490.mpd01.ams03.atlas.cogentco.com (130.117.3.106) 192.672 ms te4-1.mpd01.ams03.atlas.cogentco.com (130.117.48.62) 160.769 ms vl3490.mpd01.ams03.atlas.cogentco.com (130.117.3.106) 156.042 ms
15 cogent-1101.xe-0-0-0.jun1.kelvin.network.bit.nl (149.6.128.154) 175.695 ms 175.511 ms 175.322 ms
16 nlede01.sixxs.net (193.109.122.244) 178.562 ms 179.125 ms 181.206 ms
tracker.sixxs.net down?
Shadow Hawkins on Monday, 26 January 2009 01:02:47traceroute to tracker.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 40 byte packets
1 cl-92.dal-01.us.sixxs.net (2001:1938:80:5b::2) 157.125 ms 157.446 ms 159.444 ms
2 2001:4de0:1000:a3::2 (2001:4de0:1000:a3::2) 159.860 ms 160.289 ms 161.001 ms
3 2001:4de0:1000:a3::2 (2001:4de0:1000:a3::2) 161.378 ms 163.188 ms 164.551 ms
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 17 December 2008 16:49:30
Posting is only allowed when you are