Hi,
I represent the mirror at http://mirror.globo.com/
The last representative is no longer working in this company, and we would like take on his good work.
As part of the process, we are deploying a new mirror manager, with a new public address. This new manager host cannot rsync anymore from *us-msync.centos.org*
Is it possible to add this new address, or better yet, a range of our possible outgoing addresses?
*Previous Addr: 131.0.24.130* *Current Addr: 131.0.26.250* *Possible range: 131.0.24.0/22 and 2804:294::/32*
Is there any other info that you need from us right now?
Regards,
Jonny
João Carlos Mendes Luís kirjoitti 27.3.2018 klo 15.07:
Hi,
I represent the mirror at http://mirror.globo.com/
The last representative is no longer working in this company, and we would like take on his good work.
As part of the process, we are deploying a new mirror manager, with a new public address. This new manager host cannot rsync anymore from *us-msync.centos.org*
Is it possible to add this new address, or better yet, a range of our possible outgoing addresses?
*Previous Addr: 131.0.24.130* *Current Addr: 131.0.26.250* *Possible range: 131.0.24.0/22 and 2804:294::/32*
Hi, yes, the system does accept ranges, but we usually prefer smaller ranges than those that you specified. The idea is that the ACL entry should be big enough so that it would allow the ISP to operate their mirror, but small enough so that the ISP's customers would be outside that IP address range. We do still prefer listing specific IP addresses if possible.
In this particular case you don't seem to be in the business of providing computing capacity for your clients, so using a bigger IP address range would not violate the above principles. I have now added those two IP address ranges, so you should now be able to rsync directly from rsync://us-msync.centos.org/CentOS/