I stand corrected here; it looks like IPv6 got turned on a virtual interface as part of the roll out; the NOC didn't provide me a notification that the routes were activated.

This address is the source of the master for IPv6: 2604:7780:100:0:202:c9ff:fe4d:74be

Cheers and sorry for the confusion,
~H

On Wed, Mar 7, 2018 at 4:44 PM, Anssi Johansson <avij@centosproject.org> wrote:
Tails Hon1nbo kirjoitti 7.3.2018 klo 23.35:
Tails Hon1nbo kirjoitti 6.3.2018 klo 23.06:
/Thanks, />>//>>/however I am running into an issue; when I try to switch my syncs to />>/us-msync, I receive a Module Not Found error for "CentOS" /
This sounds like the IP addresses you specified do not match the IP addresses that are actually used. Please try these two commands from your mirror server and report their output:

rsync -4 rsync://no-access.miuku.net/keep-out
rsync -6 rsync://no-access.miuku.net/keep-out

These commands will show your actual IP addresses in the error message.

As the command shows, it's still coming from one of the same IPs I specified before in my original announce:
$ rsync -4 rsync://no-access.miuku.net/keep-out <http://no-access.miuku.net/keep-out>
@ERROR: access denied to keep-out from unknown (66.34.204.84)
rsync error: error starting client-server protocol (code 5) at main.c(1516) [Receiver=3.0.9]

OK, that IPv4 address is on the list, but how about IPv6? My guess is that your system has an IPv6 address that does not match what you wrote earlier (2604:7780:100:0:225:90ff:fe37:aad6) and rsync tries to use IPv6 by default when connecting to rsync://us-msync.centos.org/CentOS/

You could try "rsync -4 rsync://us-msync.centos.org/CentOS/" and see if it works any better. If it does, the problem is IPv6-related. The above "rsync -6 rsync://no-access.miuku.net/keep-out" command would give more information in this case.

_______________________________________________
CentOS-mirror mailing list
CentOS-mirror@centos.org
https://lists.centos.org/mailman/listinfo/centos-mirror