<div dir="ltr">Thank you Anssi for your helpful reply. If you do not mind, let's place all the subnet we have on the server into the ACL This will prevent reconfiguration on our side from having an impact on the mirror. Here are the subnets:<div><ul><li>2607:f0d0:1103:120::/64</li><li><a href="http://173.193.191.120/30">173.193.191.120/30</a><br></li><li><a href="http://173.193.171.184/29">173.193.171.184/29</a><br></li></ul><div>We will not need to work on the ACL for another five years with this configuration. I am sorry that I did not supply this information initially -- my apologies.</div></div><div><br></div><div>I will also use --ipv6 as you suggest.</div><div><br></div><div>Thank you again Anssi! Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 25, 2017 at 11:09 AM, Anssi Johansson <span dir="ltr"><<a href="mailto:avij@centosproject.org" target="_blank">avij@centosproject.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">25.3.2017, 18.10, Greg Sims kirjoitti:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
We recently added IPv6 Support to our server and requested that you add<br>
our IPv6 to the database for Rsync. The was accomplished on Mar 22.<br>
<br>
We has been having trouble updating our mirror since this time. It<br>
worked for a period of time and now it stopped. I understand there may<br>
be some propagation time for our IPv6 to reach all of your servers.<br>
After three days, I feel this should be complete.<br>
<br></span>
[snip]<span class=""><br>
Please notice the ERROR towards the bottom. We have not make any other<br>
changes but to start using IPv6. Please check our authorizations for:<br>
<br>
IPv4: 173.193.171.186, 173.193.191.120<br>
IPv6: 2607:f0d0:1103:120::2<br>
</span></blockquote>
<br>
The current system we're using is faster -- any changes done to the master ACL should propagate to all msync nodes in half an hour max.<br>
<br>
The error is indeed related to ACL. One source of problems might be the 2nd IPv4 address you mentioned here, 173.193.191.120. As that was not mentioned in your previous email, my assumption was that this address was no longer in use, so I dropped it. This may have been an incorrect assumption, my apologies for that. In addition, if my memory serves me correctly, the previous entry was actually <a href="http://173.193.191.0/24" rel="noreferrer" target="_blank">173.193.191.0/24</a>, ie. it allowed the entire subnet.<br>
<br>
In any case, I have now re-added 173.193.191.120, in case that helps. All the three IP addresses you mentioned are now allowed. You can also play with rsync's -4 and -6 options to make rsync prefer IPv4 or IPv6, respectively.<br>
<br>
One common problem is that on servers with multiple addresses, the IP address that gets used might not always be what people expect. For that, I usually recommend people to try "curl <a href="http://ip.miuku.net" rel="noreferrer" target="_blank">ip.miuku.net</a>", "curl <a href="http://ipv4.miuku.net" rel="noreferrer" target="_blank">ipv4.miuku.net</a>", "curl <a href="http://ipv6.miuku.net" rel="noreferrer" target="_blank">ipv6.miuku.net</a>", which shows the local IP address, unless proxies are involved.<br>
<br>
At this stage I'm fairly certain that those three IP addresses should be allowed to rsync. If you continue having problems, the most probable reason is that the msync.c.o see some other IP address than those listed, for one reason or another. If you can dig a bit more, that would be much appreciated.<br>
______________________________<wbr>_________________<br>
CentOS-mirror mailing list<br>
<a href="mailto:CentOS-mirror@centos.org" target="_blank">CentOS-mirror@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-mirror" rel="noreferrer" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/centos-mirror</a><br>
</blockquote></div><br></div>