Red Hat Bugzilla – Bug 1286478
LIBREPO prefers IPv6 over a private mirror
Last modified: 2016-04-03 23:16:12 EDT
Description of problem:
When DNF chooses a mirror, it selects IPv6 where it should *always* prefer a private mirror if available.
Version-Release number of selected component (if applicable): 1.1.3-1.fc22
How reproducible: 100%
Steps to Reproduce:
1. Start from a location where a private mirror should be used
2. Clean DNF cache
3. Use iptraf-ng or wireshark to monitor network activity
4. run dnf makecache
DNF uses IPv6 mirrors instead of the private mirror it got from the metalink.
Relevant DNF preferences should be:
1. Private IPv6
2. Private IPv4
3. Public IPv6
4. Public IPv4
I have verified that the private mirror shows up correctly in the metalink/mirrorlist. If I force DNF to IPv4 using the "-4" switch, DNF correctly uses the private mirror.
I have also observed this using f21's 0.6.4-7.fc21.
Librepo is responsible for mirror chose.
Any initial thoughts on this bug? It is making our on-campus private mirror practically useless, as-is.
This is probably caused by mirrormanager not knowing what the IPv4 address of the client is when it is hit via IPv6, and that IPv6 address not belonging to the suggested IP blocks for the private mirror.
In any case, I don't seen anything that could be done short of always hitting mirrormanager through IPv4.
I doubt there will be any ambition to change the existing behavior. Now that I have an understanding of what was causing this, I can work around it. I'll just close this out then.