Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
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)
Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works.
Ideas, comments, suggestions ?
On 17.05.2016 11:04, Fabian Arrotin wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
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)
Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works.
Ideas, comments, suggestions ?
I think this is a reasonable way to do that, hence rsync provides a "-4/-6" option to let you choose which internet protocol to prefer.
IMHO it is safer to have a separate v6 DNS. But this is only because there is access authorization done on IP level, in other cases I would strongly encourage to have A and AAAA records for the same name.
"msync-v6.centos.org::CentOS" sounds more semtantic to me.
Please include me in the test phase. ----------------------------------------------------- HTTP: http://mirror.spreitzer.ch/centos/
Sync schedule: Every 6 hrs Bandwidth: 1 Gbit/s Location: Zurich, Zurich, Switzerland Sponsor: Sascha Spreitzer Sponsor URL: http://spreitzer.ch IP to authorize: 2a02:168:7a0e:6:5054:ff:fe77:b410 Email contact: sspreitz@redhat.com Mirroring AltArch: no -----------------------------------------------------
PS.: Site is currently offline as of btrfs kernel freeze. (See my other post)
Kind regards Sascha
Sofia University St Kliment Ohridski ..::CENTOS.UNI-SOFIA.BG::..
Loadbalancer and rsync client Public IPv6 address: 2001:67c:20d0::38
host 2001:67c:20d0::38 8.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.0.2.c.7.6.0.1.0.0.2.ip6.arpa domain name pointer centos.uni-sofia.bg.
Also the official List of CentOS Mirrors page no provide quick information about IP version like IP4, IP4+6, only IP6.
Kind regards, ILIYAN ILIEV
----- Original Message ----- From: "Sascha Spreitzer" sspreitz@redhat.com To: "Mailing list for CentOS mirrors." centos-mirror@centos.org Sent: Tuesday, May 17, 2016 12:17:13 PM Subject: Re: [CentOS-mirror] discussion about ipv6 availability for msync.centos.org
On 17.05.2016 11:04, Fabian Arrotin wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
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)
Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works.
Ideas, comments, suggestions ?
I think this is a reasonable way to do that, hence rsync provides a "-4/-6" option to let you choose which internet protocol to prefer.
IMHO it is safer to have a separate v6 DNS. But this is only because there is access authorization done on IP level, in other cases I would strongly encourage to have A and AAAA records for the same name.
"msync-v6.centos.org::CentOS" sounds more semtantic to me.
Please include me in the test phase. ----------------------------------------------------- HTTP: http://mirror.spreitzer.ch/centos/
Sync schedule: Every 6 hrs Bandwidth: 1 Gbit/s Location: Zurich, Zurich, Switzerland Sponsor: Sascha Spreitzer Sponsor URL: http://spreitzer.ch IP to authorize: 2a02:168:7a0e:6:5054:ff:fe77:b410 Email contact: sspreitz@redhat.com Mirroring AltArch: no -----------------------------------------------------
PS.: Site is currently offline as of btrfs kernel freeze. (See my other post)
Kind regards Sascha
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hi *
[...]
On 17.05.2016 11:04, Fabian Arrotin wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
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)
Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works.
Ideas, comments, suggestions ?
[...]
Feel free to include us in the tests aswell:
-------------------------------------------------- HTTP: http://pkg.adfinis-sygroup.ch/centos/ HTTPS: https://pkg.adfinis-sygroup.ch/centos/
Sync schedule: Every 4 hrs Bandwidth: 1 Gbps Location: Switzerland (Bern) Sponsor: Adfinis SyGroup AG Sponsor URL: https://adfinis-sygroup.ch/ IPv4 to authorize: 95.128.34.165 IPv6 to authorize: 2001:618:1:129::165 Email contact: pkg[at]adfinis-sygroup.ch --------------------------------------------------
@Sascha: I think you mirror is missing on the mirror list [1]. :)
[1] https://www.centos.org/download/mirrors/
Kind regards
Michael
On 18.05.2016 09:44, Michael Hofer wrote:
@Sascha: I think you mirror is missing on the mirror list [1]. :)
Hi Michael
It is currently down, see my other post. Btrfs froze it. :) http://mirror-status.centos.org/#ch
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.
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
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 ! :-)
On 23.05.2016 10:05, Fabian Arrotin wrote:
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 ! :-)
Hi
Just tested it and it is working fine.
[root@mirror ~]# /usr/bin/rsync -vazH --delete msync6.centos.org::CentOS /var/www/html/centos
msync.CentOS.org rsync service (centosr5) --------------------------------------- [..]
receiving incremental file list ./ TIME dir_sizes filelist.gz timestamp.txt
sent 7658 bytes received 5951712 bytes 916826.15 bytes/sec total size is 165244474281 speedup is 27728.51
Kind regards Sascha
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 ?
Can you add 2620:0:b61:fab1::1:4 please?
s.
On 05/23/2016 08:39 PM, Scott wrote:
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 ?
Can you add 2620:0:b61:fab1::1:4 please?
Also can you add 2a02:2f0c:8000:14::1 for mirrors.linux.ro ? Thanks!
s. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Please add for the US Internet mirror 2605:8400:0:4::56
Thanks!
________________________________________ From: centos-mirror-bounces@centos.org [centos-mirror-bounces@centos.org] on behalf of Daniel Petre [daniel.petre@rcs-rds.ro] Sent: Monday, May 23, 2016 12:49 PM To: centos-mirror@centos.org Subject: Re: [CentOS-mirror] discussion about ipv6 availability for msync.centos.org
On 05/23/2016 08:39 PM, Scott wrote:
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 ?
Can you add 2620:0:b61:fab1::1:4 please?
Also can you add 2a02:2f0c:8000:14::1 for mirrors.linux.ro ? Thanks!
s. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
-- Daniel Petre Unified Services, RCS & RDS (Pitești)
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hi,
In Beijing, China, CERNET2
rsync -6 rsync://msync6.centos.org/CentOS/
reports
msync.CentOS.org rsync service (centosb5) .... @ERROR: Unknown module 'CentOS'
it seems that not all nodes are working?
the resolved IPv6 addr is 2605:9000:401:102::2 our IPv6 addr is 2402:f000:1:416:166:111:206:63
Cheers,
-- Justin Wong Tsinghua University TUNA Association
On Mon, May 23, 2016, at 16:05, Fabian Arrotin wrote:
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 ! :-)
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror Email had 1 attachment:
- signature.asc 1k (application/pgp-signature)
Please add 2406:f000:30f0::199 for http://mirror.0x.sg/
(mirror update rsync task pulls from 2406:f000:30f0::199 which is not the same as the AAAA record of the webserver)
On Tue, May 17, 2016 at 6:04 PM, Fabian Arrotin arrfab@centos.org wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
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)
Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works.
Ideas, comments, suggestions ?
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On Tue, May 24, 2016 at 01:52:50PM +0900, Andrew Yong wrote:
On Tue, May 17, 2016 at 6:04 PM, Fabian Arrotin arrfab@centos.org wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
Please add IPv6 for merlin.fit.vutbr.cz (CZ):
kasparek@pckasparek: ~$ host merlin.fit.vutbr.cz merlin.fit.vutbr.cz has address 147.229.176.19 kasparek@pckasparek: ~$ host merlin6.fit.vutbr.cz merlin6.fit.vutbr.cz has IPv6 address 2001:67c:1220:8b0::93e5:b013
Thanks.
On 24/05/16 08:22, Kasparek Tomas wrote:
On Tue, May 24, 2016 at 01:52:50PM +0900, Andrew Yong wrote:
On Tue, May 17, 2016 at 6:04 PM, Fabian Arrotin arrfab@centos.org wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
Please add IPv6 for merlin.fit.vutbr.cz (CZ):
kasparek@pckasparek: ~$ host merlin.fit.vutbr.cz merlin.fit.vutbr.cz has address 147.229.176.19 kasparek@pckasparek: ~$ host merlin6.fit.vutbr.cz merlin6.fit.vutbr.cz has IPv6 address 2001:67c:1220:8b0::93e5:b013
Thanks.
Thanks for the notification : if you had a AAAA record for merlin.fit.vutbr.cz, it would have been added automatically (see https://lists.centos.org/pipermail/centos-mirror-announce/2016-May/000023.ht...). I've added your IPv6 address in the ACL so please test that it works in the next 30 minutes
Also worth knowing that now msync.centos.org has AAAA record, so no need to use/test msync6.centos.org (which will even disappear as it was there for initial testing)
Cheers,
I just saw the announcement about adding IPv6 to msync.centos.org, which is fantastic news.
Will you be adding AAAAs to the regional endpoints as well (e.g., us-msync.centos.org and eu-msync.centos.org)?
Thanks, KRT
On Tue, May 24, 2016 at 12:39 AM, Fabian Arrotin arrfab@centos.org wrote:
On 24/05/16 08:22, Kasparek Tomas wrote:
On Tue, May 24, 2016 at 01:52:50PM +0900, Andrew Yong wrote:
On Tue, May 17, 2016 at 6:04 PM, Fabian Arrotin arrfab@centos.org
wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org
)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
Please add IPv6 for merlin.fit.vutbr.cz (CZ):
kasparek@pckasparek: ~$ host merlin.fit.vutbr.cz merlin.fit.vutbr.cz has address 147.229.176.19 kasparek@pckasparek: ~$ host merlin6.fit.vutbr.cz merlin6.fit.vutbr.cz has IPv6 address 2001:67c:1220:8b0::93e5:b013
Thanks.
Thanks for the notification : if you had a AAAA record for merlin.fit.vutbr.cz, it would have been added automatically (see
https://lists.centos.org/pipermail/centos-mirror-announce/2016-May/000023.ht... ). I've added your IPv6 address in the ACL so please test that it works in the next 30 minutes
Also worth knowing that now msync.centos.org has AAAA record, so no need to use/test msync6.centos.org (which will even disappear as it was there for initial testing)
Cheers,
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 24/05/16 16:17, Kevin Tower wrote:
I just saw the announcement about adding IPv6 to msync.centos.org http://msync.centos.org, which is fantastic news.
Will you be adding AAAAs to the regional endpoints as well (e.g., us-msync.centos.org http://us-msync.centos.org and eu-msync.centos.org http://eu-msync.centos.org)?
Thanks, KRT
In theory that was not needed as the backend used by the pdns nodes will detect the country/continent and so will automatically use one of the nodes in the correct region for msync.centos.org But it's true that if if one wants to force either us or eu, it's now available (pushed live some minutes ago on the pdns nodes and TTL is 120 so quite fast to propagate assuming that the ISP dns resolvers are really not overriding that - seen quite some time - )
Cheers,
Hi there,
It seems mirrors.tuna.tsinghua.edu.cn (2402:f000:1:416:166:111:206:63) was not added to the ACL yet. Would you like to check this?
Cheers, -- Justin Wong
On Tue, May 24, 2016, at 15:39, Fabian Arrotin wrote:
On 24/05/16 08:22, Kasparek Tomas wrote:
On Tue, May 24, 2016 at 01:52:50PM +0900, Andrew Yong wrote:
On Tue, May 17, 2016 at 6:04 PM, Fabian Arrotin arrfab@centos.org wrote:
Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org)
The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors
Please add IPv6 for merlin.fit.vutbr.cz (CZ):
kasparek@pckasparek: ~$ host merlin.fit.vutbr.cz merlin.fit.vutbr.cz has address 147.229.176.19 kasparek@pckasparek: ~$ host merlin6.fit.vutbr.cz merlin6.fit.vutbr.cz has IPv6 address 2001:67c:1220:8b0::93e5:b013
Thanks.
Thanks for the notification : if you had a AAAA record for merlin.fit.vutbr.cz, it would have been added automatically (see https://lists.centos.org/pipermail/centos-mirror-announce/2016-May/000023.ht...). I've added your IPv6 address in the ACL so please test that it works in the next 30 minutes
Also worth knowing that now msync.centos.org has AAAA record, so no need to use/test msync6.centos.org (which will even disappear as it was there for initial testing)
Cheers,
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror Email had 1 attachment:
- signature.asc 1k (application/pgp-signature)
On 24/05/16 17:12, TUNA mirror-admin wrote:
Hi there,
It seems mirrors.tuna.tsinghua.edu.cn (2402:f000:1:416:166:111:206:63) was not added to the ACL yet. Would you like to check this?
Cheers,
Justin Wong
The following block was automatically added in the ACL : 2402:f000:1::/48 . Doesn't that work for you ?
It works. Thanks!
-- Justin Wong
On Wed, May 25, 2016, at 00:17, Fabian Arrotin wrote:
On 24/05/16 17:12, TUNA mirror-admin wrote:
Hi there,
It seems mirrors.tuna.tsinghua.edu.cn (2402:f000:1:416:166:111:206:63) was not added to the ACL yet. Would you like to check this?
Cheers,
Justin Wong
The following block was automatically added in the ACL : 2402:f000:1::/48 . Doesn't that work for you ?
-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror Email had 1 attachment:
- signature.asc 1k (application/pgp-signature)
On 25/05/16 01:46, Matthew Taylor wrote:
Hi Fabian,
Are there any IPv6 enabled msync nodes within Australia?
Using IPv4, I hit a local node to Sydney (AS63956 - coloau.com.au):
[root@mirror01 ~]# mtr -rwc 5 -n -4 msync.centos.org Start: Wed May 25 09:32:39 2016 HOST: mirror01.digitalpacific.com.au Loss% Snt Last Avg Best Wrst StDev 1.|-- 101.0.101.65 0.0% 5 1.0 1.2 0.9 1.7 0.0 2.|-- 101.0.126.41 0.0% 5 0.9 1.2 0.7 1.9 0.5 3.|-- 101.0.127.229 0.0% 5 0.3 0.4 0.3 0.7 0.0 4.|-- 103.26.68.150 0.0% 5 0.8 0.9 0.8 1.4 0.0 5.|-- 103.52.116.41 0.0% 5 1.8 1.9 1.8 1.9 0.0 6.|-- 103.52.116.30 0.0% 5 1.3 1.4 1.3 1.5 0.0
Using IPv6, I hit a mirror in Canada (from AS10929 - netelligent.ca):
[root@mirror01 ~]# mtr -rwc 5 -n -6 msync.centos.org Start: Wed May 25 09:32:54 2016 HOST: mirror01.digitalpacific.com.au Loss% Snt Last Avg Best Wrst StDev 1.|-- 2401:fc00:0:20e::1 0.0% 5 1.3 1.1 1.1 1.3 0.0 2.|-- 2401:fc00:1:1f::2 0.0% 5 0.7 1.9 0.7 6.6 2.5 3.|-- 2401:fc00:1:24::1 0.0% 5 0.3 1.6 0.3 3.5 1.6 4.|-- 2001:218:c000:5000::79 0.0% 5 0.7 0.5 0.4 0.7 0.0 5.|-- 2001:218:0:6000::62 0.0% 5 1.4 0.7 0.5 1.4 0.0 6.|-- 2001:218:0:2000::321 0.0% 5 165.9 161.0 157.7 165.9 4.3 7.|-- 2001:418:0:2000::126 60.0% 5 158.1 158.0 157.9 158.1 0.0 8.|-- 2001:668:0:3::8000:2bf1 0.0% 5 165.3 162.9 157.6 165.3 3.3 9.|-- 2001:668:0:2::1:4611 0.0% 5 227.3 224.1 219.0 227.7 4.6 10.|-- 2001:668:0:3:ffff:0:adcd:2f2e 0.0% 5 243.7 240.6 235.2 243.7 3.9 11.|-- 2605:9000:0:f7e::2 0.0% 5 243.5 240.3 235.3 243.9 4.5 12.|-- 2605:9000:0:400b::1 0.0% 5 245.5 243.7 238.8 250.2 4.6 13.|-- 2605:9000:401:102::2 0.0% 5 243.4 243.0 235.2 257.4 9.0
Our mirror (centos.mirror.digitalpacific.com.au) is coming from the following addresses:
101.0.120.90 2401:fc00:0:20e::a0
MaxMind's GeoIP database indicates both of our IPv4 and IPv6 are located within Sydney, which is correct.
Thanks, Matt.
On 25/05/2016 02:26, TUNA mirror-admin wrote:
It works. Thanks!
-- Justin Wong
Hi Justin,
Unfortunately, we only have one msync node in Australia, but not providing IPv6 actually (I'm in contact with them and hopefully it will change soon) so yes, your findings are correct : for all requests coming from Oceania/Australia over IPv6, we're redirecting to the nodes in America ...
On 25/05/2016 15:27, Fabian Arrotin wrote:
On 25/05/16 01:46, Matthew Taylor wrote:
Hi Fabian,
Are there any IPv6 enabled msync nodes within Australia?
Using IPv4, I hit a local node to Sydney (AS63956 - coloau.com.au):
[root@mirror01 ~]# mtr -rwc 5 -n -4 msync.centos.org Start: Wed May 25 09:32:39 2016 HOST: mirror01.digitalpacific.com.au Loss% Snt Last Avg Best Wrst StDev 1.|-- 101.0.101.65 0.0% 5 1.0 1.2 0.9 1.7 0.0 2.|-- 101.0.126.41 0.0% 5 0.9 1.2 0.7 1.9 0.5 3.|-- 101.0.127.229 0.0% 5 0.3 0.4 0.3 0.7 0.0 4.|-- 103.26.68.150 0.0% 5 0.8 0.9 0.8 1.4 0.0 5.|-- 103.52.116.41 0.0% 5 1.8 1.9 1.8 1.9 0.0 6.|-- 103.52.116.30 0.0% 5 1.3 1.4 1.3 1.5 0.0
Using IPv6, I hit a mirror in Canada (from AS10929 - netelligent.ca):
[root@mirror01 ~]# mtr -rwc 5 -n -6 msync.centos.org Start: Wed May 25 09:32:54 2016 HOST: mirror01.digitalpacific.com.au Loss% Snt Last Avg Best Wrst StDev 1.|-- 2401:fc00:0:20e::1 0.0% 5 1.3 1.1 1.1 1.3 0.0 2.|-- 2401:fc00:1:1f::2 0.0% 5 0.7 1.9 0.7 6.6 2.5 3.|-- 2401:fc00:1:24::1 0.0% 5 0.3 1.6 0.3 3.5 1.6 4.|-- 2001:218:c000:5000::79 0.0% 5 0.7 0.5 0.4 0.7 0.0 5.|-- 2001:218:0:6000::62 0.0% 5 1.4 0.7 0.5 1.4 0.0 6.|-- 2001:218:0:2000::321 0.0% 5 165.9 161.0 157.7 165.9 4.3 7.|-- 2001:418:0:2000::126 60.0% 5 158.1 158.0 157.9 158.1 0.0 8.|-- 2001:668:0:3::8000:2bf1 0.0% 5 165.3 162.9 157.6 165.3 3.3 9.|-- 2001:668:0:2::1:4611 0.0% 5 227.3 224.1 219.0 227.7 4.6 10.|-- 2001:668:0:3:ffff:0:adcd:2f2e 0.0% 5 243.7 240.6 235.2 243.7 3.9 11.|-- 2605:9000:0:f7e::2 0.0% 5 243.5 240.3 235.3 243.9 4.5 12.|-- 2605:9000:0:400b::1 0.0% 5 245.5 243.7 238.8 250.2 4.6 13.|-- 2605:9000:401:102::2 0.0% 5 243.4 243.0 235.2 257.4 9.0
Our mirror (centos.mirror.digitalpacific.com.au) is coming from the following addresses:
101.0.120.90 2401:fc00:0:20e::a0
MaxMind's GeoIP database indicates both of our IPv4 and IPv6 are located within Sydney, which is correct.
Thanks, Matt.
On 25/05/2016 02:26, TUNA mirror-admin wrote:
It works. Thanks!
-- Justin Wong
Hi Justin,
Unfortunately, we only have one msync node in Australia, but not providing IPv6 actually (I'm in contact with them and hopefully it will change soon) so yes, your findings are correct : for all requests coming from Oceania/Australia over IPv6, we're redirecting to the nodes in America ...
Hi Fabian,
Thanks for the response.
I should have bottom posted, rather than top. :)
I believe we can assist with providing another msync node within Australia. Perhaps we can take this off-list to discuss?
Regards, Matthew.
24.5.2016, 9.22, Kasparek Tomas kirjoitti:
Please add IPv6 for merlin.fit.vutbr.cz (CZ):
kasparek@pckasparek: ~$ host merlin.fit.vutbr.cz merlin.fit.vutbr.cz has address 147.229.176.19 kasparek@pckasparek: ~$ host merlin6.fit.vutbr.cz merlin6.fit.vutbr.cz has IPv6 address 2001:67c:1220:8b0::93e5:b013
In general, in this day and age it is recommended to just add an AAAA DNS record for the main mirror hostname instead of creating a new IPv6-only hostname.
When clients access mirrorlist.centos.org over IPv6, they will receive only mirrors that are available over IPv6. See curl -6 'http://mirrorlist.centos.org/?repo=os&arch=i386&release=6&cc=cz'
This means that IPv6-enabled CentOS installations within your network are currently being directed to use some other mirror instead of your local mirror.
If you add an IPv6 DNS entry for your mirror, the IPv6 mirror crawler will pick up the change automatically within a few hours and add the mirror to the list of IPv6-enabled mirrors.
-
Andrew Yong -
Anssi Johansson -
Daniel Petre -
Fabian Arrotin -
Iliyan Iliev -
Justin Krejci -
Kasparek Tomas -
Kevin Tower -
Matthew Taylor -
Michael Hofer -
Sascha Spreitzer -
Scott -
TUNA mirror-admin