mirror

mirror@lists.centos.org

2 participants
4583 discussions

Start a nNew thread

mirror list
by Jeremias Paras 25 Oct '11

25 Oct '11

acolytes29(a)gmail.com

1 0

Public Mirror list
by Supporto Tecnico - Crazy Network 25 Oct '11

25 Oct '11

2 2

mirror.umoss.org -> mirror.umd.edu
by UMLUG 24 Oct '11

24 Oct '11

Our mirror has moved from mirror.umoss.org to mirror.umd.edu. We are now carrying the entire CentOS tree, and we have added FTP access. Our addresses are now: http://mirror.umd.edu/centos/ rsync://mirror.umd.edu/centos/ ftp://mirror.umd.edu/centos/

2 1

directly dvd acces no
by Mj Webhosting 24 Oct '11

24 Oct '11

Hello, We are syncen a couple of times a day. And when we go to the status page we are not showing that we have directly dvd access. Is this possible to change that? Greetz, MichaËl Jonkers Mj Webhosting

2 2

DVD access
by David Bunt 24 Oct '11

24 Oct '11

Our IP address changed for mirror.teklinks.com The new IP is 207.223.121.100 Can you change the dvd acl please sir? -- David Bunt Data Center Operations - Linux TekLinks Managed Services Group p. 205.278.7252 e. dbunt(a)teklinks.com Please direct all support questions to our customer support team available at 205.314.6634 or hosting(a)teklinks.com

2 1

IPv6 Bittorrent tracker for CentOS torrents
by Anssi Johansson 23 Oct '11

23 Oct '11

Hi, this message is related to the enhancement request I filed at http://bugs.centos.org/view.php?id=4652 where I proposed to have an IPv6-enabled CentOS torrent tracker. I've been operating a torrent seedbox at http://norsu.miuku.net/ for about a year now and it has been pushing bits at a rate of about 5TB/month. It's not restricted to serving only CentOS data, but I'd estimate that it has served about 5TB of CentOS data in total so far. Yes, I know there are proper mirror servers which have traffic amounts much higher than that, but that's beside the point. My primary goal with setting up that torrent seedbox was to increase the amount of bits transferred over IPv6, as in, I'd serve primarily IPv6 clients and IPv4 clients would get only the leftover bandwidth. Unfortunately the amount of IPv6 traffic is still quite low, but I'd like to help in changing that trend, even if only by a tiny amount. I'm a computer science student nowadays and my studies concentrate on computer networks, thus IPv6 adoption is a particularly interesting subject to me. Besides the fact that there might not be that many IPv6-enabled hosts downloading data with bittorrent, there's also a technical problem which hinders IPv6 usage with bittorrent. Obviously most IPv6-capable peers are also able to connect to IPv4 trackers, so that's not the problem. The problem is how the tracker gets to know the client's IPv6 address if the client connects to the tracker with IPv4. And if the tracker doesn't know the client's IPv6 address, it can't tell that IPv6 address to other clients connecting to the tracker, thus forcing clients to connect to each other using IPv4 even if they were both IPv6 enabled. There are bittorrent protocol extensions that allow the client to include the IPv6 address in the data when connecting to the tracker, but my experience shows that most trackers seem to either not implement those protocol extensions, or intentionally disregard any extra IP address information. By having a tracker with an IPv6 address, the tracker can simply record the source address of the connection. The problem is that CentOS has only an IPv4 tracker at this moment. I'd suggest setting up a separate tracker that would be accessible via IPv6. As a proof of concept, I have set up an instance of OpenTracker (compiled from source from http://erdgeist.org/arts/software/opentracker/) on a separate IPv6-enabled server; some assorted files of that tracker can be seen at http://tursas.miuku.net/tracker/ I have also modified (with the help of torrenteditor.com) some existing CentOS 6 torrents to include my IPv6-enabled tracker. These torrent files can be found at http://norsu.miuku.net/torrents/ipv6/ Those torrents could be placed in the appropriate place so that they'd get used for any new CentOS 6 downloads. Please note that even though the torrents have been modified to include an additional tracker, the info hash is unchanged. This means that the torrent swarm won't be split even if someone now starts using the new torrents. Using these modified torrents now would enable us to test the new tracker with a bit less traffic, as compared to trying the new tracker only when C6.1/C5.8 is eventually released. I offered to maintain this IPv6 torrent tracker server myself for the benefit of the CentOS community. The offer is still valid, but Karanbir suggested that there might already be some CentOS servers which might be suitable for this purpose. Someone with the appropriate privileges would need to set up the IPv6 tracker on some IPv6-enabled server and set up an AAAA record pointing to that server (perhaps named ipv6.torrent.centos.org, as in my modified torrents). The torrent creation scripts would need to be updated to include "-a http://torrent.centos.org:6969/announce -a http://ipv6.torrent.centos.org:6969/announce", assuming you're using the standard mktorrent. Please note that "-a URL1,URL2" would create a different kind of torrent than "-a URL1 -a URL2". The "-a URL1 -a URL2" method is preferred as it'll create two separate tracker groups. My focus point with this project is on dual-stacked machines -- if the machine has a possibility to download the torrent data over IPv4 or IPv6, I'd prefer that it'd be done over IPv6. This is slightly different than the IPv6 mirrorlist project that was discussed on this list some time ago, as it was aimed at IPv6-only networks. In particular, we wouldn't need to have IPv6 connectivity for centos.org name servers for this IPv6 tracker project. I feel that setting up an IPv6 torrent tracker wouldn't be that much of work and it'd signal that CentOS is doing its share when it comes to IPv6 adoption. Perhaps the forthcoming CentOS 6.1 torrents will already include the new IPv6 torrent tracker?

3 4

Re: [CentOS-mirror] confirm 86400f46de8e95328a08613440f583cfdd3102db
by Jawed Amin 20 Oct '11

20 Oct '11

On Thu, Oct 20, 2011 at 1:04 PM, <centos-mirror-request(a)centos.org> wrote: > Mailing list subscription confirmation notice for mailing list > CentOS-mirror > > We have received a request from 203.135.38.89 for subscription of your > email address, "jawedamin(a)gmail.com", to the centos-mirror(a)centos.org > mailing list. To confirm that you want to be added to this mailing > list, simply reply to this message, keeping the Subject: header > intact. Or visit this web page: > > > http://lists.centos.org/mailman/confirm/centos-mirror/86400f46de8e95328a086… > > > Or include the following line -- and only the following line -- in a > message to centos-mirror-request(a)centos.org: > > confirm 86400f46de8e95328a08613440f583cfdd3102db > > Note that simply sending a `reply' to this message should work from > most mail readers, since that usually leaves the Subject: line in the > right form (additional "Re:" text in the Subject: is okay). > > If you do not wish to be subscribed to this list, please simply > disregard this message. If you think you are being maliciously > subscribed to the list, or have any other questions, send them to > centos-mirror-owner(a)centos.org. >

1 0

Finish rsync
by Joao Paulo Saldanha 19 Oct '11

19 Oct '11

I'm already finished sincronization. What's next step to publish my mirror? Anyone can help me? I would like publish with http, ftp and rsync for another peoples. Wait. -- * *

3 3

dvd access
by Mj Webhosting 18 Oct '11

18 Oct '11

Hello everyone, Would it be possible to get access to for centos.mirror.mjwebhosting.nl (46.249.43.24) to msync-dvd.centos.org::CentOS-incdvd?

3 11

Mirrormanager (now for real)
by Ralph Angenendt 18 Oct '11

18 Oct '11

Hey, long time no infrastructure changes (well, on the CentOS side, quite a few on my side). As several people have offered to help moving our selfbotched system to mirrormanager (sorry Peter, but there were some offers - I am still not sure which one really is better technically, but the more helping hands, the better), I'd like to start this now. First question: I guess as a first move we need a machine to host that on. Can anyone running a mirrormanager instance tell me, what kind of specs that machine needs to have? Does it need to hold a copy of the mirror? On the software side, I guess httpd and mysql-server (and mirrormanager) - anything else? Or is the sqlite variant fast enough for the amount of mirrors we have? At the moment we run quite a few instances of mirrorlist.centos.org - the machines which hand out the urllist to machines - is that possible with mirrormanager, too? Or will one machine be able to handle the load? Depending on your answers I am going to snatch a machine from our pool for setting that up, next week. And with that machine we can start building, testing and then deploying mirrormanager. I am away over the weekend, so please don't expect answers - or more questions - from me before monday evening :) Cheers, Ralph

3 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

mirror