28.2.2017, 7.48, JeanPaul van der Mijle kirjoitti: > Hello, > > We NFOrce Entertainment B.V. have enabled IPv6 on the mirror for a while > but noticed this was not whitelisted in the rsync. > > HTTP: http://mirror.nforce.com/CentOS/ > FTP: ftp://mirror.nforce.com/CentOS/ > RSYNC: rsync://mirror.nforce.com/CentOS/ > > Sync schedule: Every 4 hrs > Bandwidth: 10GBPS > Location: Amsterdam,Netherlands > Sponsor: NFOrce Entertainment B.V. > Sponsor URL: http://www.nforce.com/ > IP to authorize: 85.159.239.121 , 2a00:1768:1000:22:1::1 > Email contact: noc at nforce.com > > I will force IPv4 for now in the rsync. Thank you. Thanks, this change has now been done and the changes are heading towards all our msync nodes, so you should be able to rsync over IPv6 soon. The more IPv6 bits the merrier. I didn't change the URLs, because the ones currently listed on https://www.centos.org/download/mirrors/ for your mirror seem to match your current setup. You may need to do some more fine tuning to your IPv6 setup, though. There are some problems connecting to your mirror over IPv6: $ telnet mirror.nforce.com ftp Trying 2a00:1768:1000:22:1::1... telnet: connect to address 2a00:1768:1000:22:1::1: Connection refused Trying 85.159.239.121... Connected to mirror.nforce.com. Escape character is '^]'. 220 (vsFTPd 3.0.2) $ telnet mirror.nforce.com rsync Trying 2a00:1768:1000:22:1::1... telnet: connect to address 2a00:1768:1000:22:1::1: Connection refused Trying 85.159.239.121... telnet: connect to address 85.159.239.121: Connection refused In the rsync case, there are also problems with IPv4. Thanks for having a look at this problem :)