On Wed, Mar 14, 2018 at 01:30:15PM +0000, Tom W wrote:
In running our mirror of EPEL at UKFast, we have noticed that many of
our own IP ranges and indeed the AS do not use our own mirror, but another nearby one. As
I understand it, with "ASN Clients?" ticked and the IPs/ASN being correct, this
should force all within our ASN and those IP ranges to use our mirror if my thinking is
correct?
This is is almost correct. Your mirror should be the one with the
highest priority, but not the only mirror.
Looking at the manual latency tests performed by fastestmirror, it
does look like due to the proximity of the other mirror they may get a response in
marginally faster. Is there a way to guarantee all of our own AS/IP ranges uses our own
mirror instead of external ones? There are no server-side limitations to HTTP/HTTPS
traffic which might cause it to be unavailable.
Not really familiar with fastestmirror (, besides that I disable it most
of the time) . So, your mirror should be the one with the highest
priority from MirrorManager. The result from MirrorManager will always
return additional mirrors with lower priority to make sure the users
always get multiple mirrors to choose from, in case one of them is not
available.
So to actually answer your questions, it is not possible to only return
mirrors in your ASN/site-local netblocks. There are always more, if
available, with a lesser priority, to make sure there is always a
working mirror returned to the user.
The problem seems to be that fastestmirror does not honor the ordering
of MirrorManager.
Adrian