Pacman-mirrors and dual-stack: limit connection to IPv4

My ISP supplies “dual-stack” instead of “IPv6 nativ” - therefore no IPv6 adresses. Fact.

As repo.manjaro.org has only IPv4,
the command “pacman-mirrors” needs some minutes until it connects.
If I block IPv6 in Network-Preference - then its as fast as heaven/hell.

Great you solved the puzzle :+1:

Hello youngster: :innocent:

And now: how to convince which Developer to change the behavior of “pacman-mirrors”…

Hello grandpa - :raised_hand: - pacman-mirrors is a python application - there is really nothing which can be done - as it uses active system network.

pacman-mirrors doesn’t care if it is IPv4 or IPv6 - all it cares about is connection.

curl --ipv6 https://manjaro.moson.eu/pool/overlay/autogit-1.0-1-any.pkg.tar.zst --output testfile
limits connections to IPv6 Adresses for example. On my machine this fails (timeout).

But that has nothing to do with pacman-mirrors as an application…

This is probably a configuration issue beyond my IPv4 knowledge :slight_smile: and most likely local to your ISP and/or your local network.

Niemand versteht mich - wo bleibt Odysseus??
Maybe @philm can help

Ahh Ich verstehe - but I think you are mixing concepts here.

If manjaro.moson.eu is in fact providing IPv6 address - an AAAA-record - and your curl command cannot translate the hostname into an IPv6 address then it is a configuration issue - but it is impossible to know if this is on your side or your ISP.

If you run pacman -Syy - what happens then? - that implies your primary mirror is manjaro.moson.eu.

Are you running a local DNS - bind or pihole - anything but the default ISP config for your router/modem?

EDIT.

I did a search for python and IPvX connection but I still think it is a configuration issue on your side.

:: Synchronisiere Paketdatenbanken...
 core                                         166,8 KiB  4,40 MiB/s 
 extra                                      2001,3 KiB  6,65 MiB/s
 community                                6,5 MiB  6,75 MiB/s
 multilib                                   181,2 KiB  7,37 MiB/s 

Comes fast, response at instance.
.
configuration issue on your side - no, i can get no IPv6 Adresses neither Windows can.
(DUAL-STACK)

dig repo.manjaro.org
; <<>> DiG 9.16.12 <<>> repo.manjaro.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50594
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;repo.manjaro.org.		IN	A

;; ANSWER SECTION:
repo.manjaro.org.	60855	IN	A	116.203.249.219

;; Query time: 6 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Fr Mär 12 17:24:00 CET 2021
;; MSG SIZE  rcvd: 61

dig repo.manjaro.org  AAAA                                                                                                                                                    

; <<>> DiG 9.16.12 <<>> repo.manjaro.org AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39644
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;repo.manjaro.org.		IN	AAAA

;; AUTHORITY SECTION:
manjaro.org.		3591	IN	SOA	ns1.first-ns.de. dns.hetzner.com. 2021031104 14400 1800 604800 86400

;; Query time: 0 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Fr Mär 12 17:25:22 CET 2021
;; MSG SIZE  rcvd: 111

yeah. repo.manjaro.org probably does not have an ipv6 address. This is not something pacman-mirrors can do anything about though…
And Manjaro does not control the mirrors, so there is no way to ensure that they have an ipv6 address either.

Dual-Stack means you get a public IPv4 as well as IPv6 address. Fact!

Is IPv6 enabled on your router at all?

https://avm.de/service/fritzbox/fritzbox-7590/wissensdatenbank/publication/show/573_IPv6-Unterstutzung-in-FRITZ-Box-einrichten/

2 Likes

Everything done avm Wissensdatenbank. Result: https://test-ipv6.com/

Bildschirmfoto vom 2021-03-13 10-12-15

Look like a timing problem: IPv4 comes faster than IPv6 (?).
++++

Internetverbindung

IPv4: Verbunden seit 11.03.2021, 17:21 Uhr, Telekom, Geschwindigkeit des Internetzugangs (verfügbare Bitrate): ↓61,7 Mbit/s ↑12,4 Mbit/s
IPv6: Verbunden seit 11.03.2021, 17:21 Uhr, Telekom, Geschwindigkeit des Internetzugangs (verfügbare Bitrate): ↓61,7 Mbit/s ↑12,4 Mbit/s

https://ipv6-test.com/

Looks like you don’t have an IPv6 address.
ip addr

ip addr                                                                                                                                                                       
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d4:5d:64:b7:a3:35 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.xx/yy brd 192.168.178.255 scope global dynamic noprefixroute enp6s0
       valid_lft 863778sec preferred_lft 863778sec
    inet6 2003:e3:9f28:fd00:82f4:5047:16d2:3876/64 scope global dynamic noprefixroute 
       valid_lft 6980sec preferred_lft 1083sec
    inet6 fe80::66f5:a2a:c639:3105/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Seems your have a global ipv6 address.
Maybe your ISP just sucks with ipv6 lol.

What exactly did you configure on the fritzbox in the IPv6 settings?

i use also ipv6 (not use FRITZ) and no timeout for me: ipv6 or v4 change nothing for pacman-mirrors

2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 6c:62:6d:4c:f2:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.25/24 brd 192.168.0.255 scope global dynamic noprefixroute enp2s0
       valid_lft 42124sec preferred_lft 42124sec
    inet6 2a01:XXX:90b:XXXX:f344:c6c1:4351:1902/64 scope global dynamic noprefixroute 
       valid_lft 86400sec preferred_lft 86400sec
    inet6 fe80::XXX:5380:XXXX:5cab/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Exactly this (checked 3 times):

https://avm.de/service/fritzbox/fritzbox-7590/wissensdatenbank/publication/show/573_IPv6-Unterstutzung-in-FRITZ-Box-einrichten/

But what option exactly.
There are different options to configure it.

Should be like this:

This doesnot work else with activated/deactivated “DHCPv6 Rapid Commit verwenden”.
And “Native IPv4-Anbindung verwenden” , with activated/deactivated “DHCPv6 Rapid Commit verwenden”.
kein Unterschied…
Die verbindung zu repo.manjaro.org dauert mit den vorgeschlagenen Einstellungen bis zu 5 Minuten,
wenn ich in Einstellungen/Netzwerk die IPv6 deaktiviere oder auf “Automatisch, nur DHCP” stelle,
kommt die Antwort “sofort”.


Wie ist das eigentlich:
repo.manjaro.org hat nur eine IPv4 Adresse.
Sagt der Server mir Bescheid, das IPv6 nicht zu haben ist, oder macht er ein timeout von 2 Minuten
auf solch eine unverschämte Anfrage (hast du IPv6) und meldet dan Fehler, worauf mein PC
sich dazu herablässt, eine IPv4 Adresse zu verlangen?
.
How is that actually:
repo.manjaro.org has only one IPv4 address.
Does the server tell me that IPv6 is not available or does it timeout for 2 minutes
on such an outrageous request (do you have IPv6) and then reports an error, what my PC
condescends to ask for an IPv4 address?
+++++
ip -6 route show default
default via fe80::464e:6dff:fe69:a22 dev enp6s0 proto ra metric 20100 pref medium