Since the latest AVM Fritz!Box 7590 Update (7.25)
ipv6 falls back to ipv4 by accident.
. -----------------------------------------------------------------------
EDIT:
Mystirious log while doing “sudo pacman-mirrors -i”:
Mär 06 17:52:25 ***** systemd-resolved[676]: DNSSEC validation failed for question ping.archlinux.org IN AAAA: incompatible-server
Mär 06 17:52:25 ***** systemd-resolved[676]: DNSSEC validation failed for question ping.archlinux.org IN A: incompatible-server
Mär 06 17:52:25 ***** systemd-resolved[676]: DNSSEC validation failed for question ping.archlinux.org IN A: incompatible-server
Mär 06 17:52:25 ***** systemd-resolved[676]: DNSSEC validation failed for question ping.archlinux.org IN AAAA: incompatible-server
Mär 06 17:52:25 ***** systemd-resolved[676]: DNSSEC validation failed for question ping.archlinux.org IN AAAA: incompatible-server
The master repo server does not have a IPv6 address as the addition of an AAAA record has proved to negatively affect almost the entire mirror pool - but you already know that.
My network DNS resolver runs on an early raspberry pi but the master repo server does not.
If you experience long response to a simple json text file - then you have serious network issues - whether that is local or ISP related I cannot possibly know.
timed pacman-mirrors -c de
➜ ~ sudo time pacman-mirrors -c de
::INFO Downloading mirrors from repo.manjaro.org
::INFO User generated mirror list
::------------------------------------------------------------
::INFO Custom mirror file saved: /var/lib/pacman-mirrors/custom-mirrors.json
::INFO Using custom mirror file
::INFO Querying mirrors - This may take some time
..... Germany : https://manjaro.re/
1.899 Germany : http://manjaro.re/
0.335 Germany : https://manjaro.moson.eu/
0.134 Germany : http://manjaro.moson.eu/
::INFO Writing mirror list
::Germany : https://manjaro.moson.eu/unstable/$repo/$arch
::Germany : https://manjaro.re/unstable/$repo/$arch
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run 'sudo pacman-mirrors -c all'
0.32user 0.03system 0:08.05elapsed 4%CPU (0avgtext+0avgdata 32380maxresident)k
0inputs+96outputs (0major+5143minor)pagefaults 0swaps
I suggest you begin with disabling IPv6 at the critical points - your router, dns and dhcp. If you have no IPv6 enabled at these points any device using a private IPv6 broadcast - what-ever - will have to use IPv4.
If it is your router - disabling IPv6 at that point will force all your clients to use IPv4 - of course if you run a campus with 500.000 devices including smart-light, refrigerators, fridges, smartphones, mouses, rats and students - everyone with a minimum of 4 devices (laptop, workstation, phone, tablet) - then you will probably be forced to use IPv6 - until that happens - hasta-la-vista IPv6.
My network services are configured for IPv4 only and I have no intention of learning how IPv6 works. I deliberately disable IPv6 when it is insisting on interfering with my network setup.
The same issue on a second PC with Ubuntu 20.4?!
My router says - ipv6 is availabel - the Firefox loads ipv6 sites, but after same time if i reload, its ipv4.
May be an ISP problem since End of October 2020 (logs say so).
Or the Fritz!Box update to 7.25 firmware. Before this - no networkproblems. Or accident?
I need some IPv6 only sites, so disabling IPv6 is not the right way, old man. (o.K.I am aged 69).
But finally:
10 print “Thank You”
20 goto 10
xxxxxxxxxxxxxxxxxxx(Tante) Edit:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Habe gerade eine mögliche Lösung gefunden:
Einstellungen → Netzwerk IPv4 “DNS Automatisch” deaktiviert und IPv6 “DNS"Automatisch” aktiviert.
.
danach lief das Updaten der Pamac Datenbank so etwas von schnell, das mir schwindlig wurde…
Well - then you outrank me ol’man - I am only reaching 61 this year been on sick leave - then retired since 2008 - sold off - more like - gave away my business - to some ungrateful sob.
TL:DR
the request fetching the json data files containing mirrors and current status lacked a timeout.
This has been added and a new version is in unstable 4.19.3 - I wonder if your IPv6 issue is somehow connected to these specific calls lacking a timeout?
Testing.
pacman-mirrors -v
Version 4.19.3
.
sudo pacman-mirrors -i [1]
::WARNING https://gitlab.manjaro.org ‘HTTP Error 500: Internal Server Error’
::WARNING https://gitlab.manjaro.org ‘HTTP Error 500: Internal Server Error’
::INFO Downloading mirrors from repo.manjaro.org
Traceback (most recent call last):
File “/usr/bin/pacman-mirrors”, line 28, in
pm.run()
File “/usr/lib/python3.9/site-packages/pacman_mirrors/pacman_mirrors.py”, line 101, in run
httpFn.download_mirror_pool(config=self.config, tty=self.tty, quiet=self.quiet)
File “/usr/lib/python3.9/site-packages/pacman_mirrors/functions/httpFn.py”, line 196, in download_mirror_pool
result = download_mirrors(config)
File “/usr/lib/python3.9/site-packages/pacman_mirrors/functions/httpFn.py”, line 59, in download_mirrors
with urllib.request.urlopen(req, timeout=config[“timeout”]) as response:
KeyError: ‘timeout’
happened to me too - while programming AMIGA in last Century.
.
Btw.: I decided to reset my Fritz!Box to factory settings and let the Telekomiker configure the FB automagic.
Now it works even better than before - digital daemons at work???
Old swedish - no, but denmarkish I presume.