Repository navigation
Optional IPV6 support for mirror checks #523
Description
Hi,
When adding or having an existing mirror inside archweb, one cannot control if IPV6 support is added or not. There has been cases where IPV6 is broken via mirror checks but they still use it or a failed ipv6 check is what is causing a bad mirror score for an otherwise healthy mirror (if ipv6 is not intended)
If I understand correctly, authenticated users in archweb can only see them as readonly fields
Line 36 in 31333d3
One Idea would be that we keep the same functionality but the fields become auto-ticked checkboxes if the mirror has either A or AAAA record. So one may disable either for whatever reason.
Activity
[-]Optioanl IPV6 support for mirror checks[/-][+]Optional IPV6 support for mirror checks[/+]jelly commentedon Aug 19, 2024
So we have a service called
mirrors/management/commands/mirrorresolv.pywhich sets thehas_ipv4andhas_ipv6fields and this is buggy? Then why don't we fix the issue of resolving if the mirror has ipv4 or ipv6?Do you know a mirror which was wrongly shown as broken?
pitastrudl commentedon Aug 23, 2024
Hey, the issue is with this mirror: https://archlinux.org/mirrors/huongnguyen.dev/. Currently still ongoing.
This could be a good idea, so we keep the same functionality. How would we go about fixing it? This is only doing resolving but not if the mirror endpoint is reachable or not, should we do a port test?