We do have a Xen host and several VMs on native IPv6 hosted at ibiblio.org, which is where we would want to run such a tracker ourselves if possible. The goal was to run the opentracker-v6 in parallel with the existing bittorrent-based tracker. http://fedoraproject.org/wiki/Infrastructure/IPv6 notes our v6 infrastructure. The problem wasn't just that statistics were unavailable (which would be a problem - we like having some counts of download methods), but that even retrieving them via http would crash the tracker. :-( I looked into Azureus briefly, but IIRC it's java-based? We don't have any java in our infra environment right now. That doesn't mean we couldn't add it, but most FI maintainers aren't java experts. I haven't looked into BitTornado. Thank you for your offer to host though - that's something we can consider. The infrastructure list (copied) is the right place for this discussion. Anyone else have thoughts on this? -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux ________________________________________ From: Bernhard Schmidt [berni@xxxxxxxxxxxxx] Sent: Saturday, February 13, 2010 11:19 AM To: Domsch, Matt Cc: admin@xxxxxxxxxxxxxxxxx; infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: Additional IPv6 Bittorrent tracker On Sat, Feb 13, 2010 at 11:08:31AM -0600, Matt_Domsch@xxxxxxxx wrote: Hi Matt, there are not that many trackers that support IPv6 as of now. The only others I know are Azureus/Vuze and (limited) BitTornado. However, this mail was about running a Tracker on IPv6, not changing the currently used tracker software to OpenTracker. You need IPv6 connectivity to run the IPv6 tracker though, which does not seem to be in use in the Fedora infrastructure at the moment (as far as I could tell). This is why I volunteered my system, running opentracker, to be used by Fedora. I haven't had any stability issues, although I have to agree with you that statistics are a weak point (by design?) of opentracker. Best Regards, Bernhard > We have been looking at using opentracker, but it has been slow going, > with us finding several bugs and needing to resolve those. Last I > knew, extracting statistics from it was difficult and prone to > crashing. If that's resolved now, we could use opentracker, but I > haven't looked in a few weeks to know. > > > -- > Matt Domsch > Technology Strategist, Dell Office of the CTO > linux.dell.com & www.dell.com/linux > > ________________________________________ > From: Bernhard Schmidt [berni@xxxxxxxxxxxxx] > Sent: Saturday, February 13, 2010 9:17 AM > To: admin@xxxxxxxxxxxxxxxxx > Subject: Additional IPv6 Bittorrent tracker > > Hi, > > as most of you probably know IPv6 is the upcoming successor of the > current internet protocol IPv4. I have recently started to look into the > Bittorrent over IPv6 situation (my summary is available at > http://www.birkenwald.de/dokuwiki/doku.php?id=projects:ipv6-bittorrent > ). > > Currently, while most Bittorrent clients are IPv6-capable most trackers > are not. This makes it very hard to impossible for clients to find IPv6 > peers on their own. > > The Bittorrent Multitracker extensions, which are implemented in almost > any client known today (and still provide a full backup path for clients > not implementing it) allow multiple trackers to be specified for a > torrent. We have recently done this for the conference recordings of > 26c3 (a big german hacker conference) and had good results. The same > scheme is now in action for Ubuntu and Knoppix. The OpenOffice project > gave positive feedback, but has not implemented it so far. > > Therefor I'd like to ask you to put an IPv6-only tracker into the Fedora > torrents. If there is a need I would volunteer to run that (see the > URL) and I also have a few very high-speed seeders (>= 1Gbps) on native > v6 that can help out to seed. But as stated before, this would only be > an additional tracker, not replacing the current one. > > Please tell me what you think about this. > > Best Regards, > Bernhard -- _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
