On 19/05/16 15:15, Fabian Arrotin wrote:
On 18/05/16 20:57, Scott wrote:
So the idea would be to have something like msync-v6.centos.org::CentOS-v6, and ask you to provide us the ipv6 address for your mirror (we can already do that in advance if you advertise AAAA record on your side for your mirror) and so it would be an "opt-in" thing (at least as a start)
The separate DNS ensures that people will only get what they ask for (v4 or v6), but why have a separate module name? Put both v4 and v6 acls on the CentOS module and clients will get the one matching the DNS name they use.
Scott.
Yes, that's the plan so msync-v6.centos.org::CentOS . I pushed yesterday {cloud,debuginfo,vault,buildlogs} AAAA records (in our GeoIP/PDNS backend) so now working on the msync part (and then mirror.centos.org too)
Stay tuned
So, I just pushed today msync6.centos.org and I also added the ipv6 addresses from this thread in the CentOS rsync module acl. So can you test that you can sync over ipv6 by using the following host/path : msync6.centos.org::CentOS ?
After some positive feedback I'll make a bigger/wider announce for the ipv6 availability for msync and also add mirror.centos.org too
Thanks for your feedback ! :-)