In all of my computers and servers (running Devuan of course), I previously also had issues accessing deb.devuan.org and some of its mirror servers.
From what I had observed, the issue happened when the repositories used IPv6.
So I included a file with the name of 00force-ipv4 in /etc/apt/apt.conf.d which contains the following line:
Acquire::ForceIPv4 "true";
Since then I have never had any issue any more.
Kind regards,
Anto
On 26/02/2022 14:50, tito via Dng
wrote:
On Sat, 26 Feb 2022 13:49:50 +0100 Radisson via Dng <dng@lists.dyne.org> wrote:Am 24.02.22 um 18:35 schrieb goli...@devuan.org:On 2022-02-24 10:08, Radisson via Dng wrote:Hi List, i tried to update daedalus but i have problems to reach deb.devuan.org 101 network is unreachable. Is that expected ? what is the alternative ? re, prYou need to use http unless you choose a specific mirror that serves https. http://pkgmaster.devuan.org/mirror_list.txt Perhaps that's the problem?sorry for the delay .. no i have successfully installed last year, ntl i have checked again and is http. I am connected via a proxy (that was no problem before) When i try to reach that dev.devuan.org via browser i have the same problem and i get back a IPv6 address, maybe an ipv4-v6 issue ? I have no problem with pkgmaster.devuan.org (looking at mirror_list.txt). so the problem leaves me confused ... I picked fau.de from the mirror list and it seems to work, i guess it is an ipv4/6 issue somewhere in between. Is it possible that deb.devuan.org is reachable via IPv6 only ? re,Hi, there seem to be some IPV6 hosts: nslookup deb.devuan.org Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: deb.devuan.org canonical name = deb.rr.devuan.org. Name: deb.rr.devuan.org Address: 185.178.192.43 Name: deb.rr.devuan.org Address: 185.203.114.135 Name: deb.rr.devuan.org Address: 185.38.15.81 Name: deb.rr.devuan.org Address: 185.183.113.131 Name: deb.rr.devuan.org Address: 46.4.50.2 Name: deb.rr.devuan.org Address: 160.16.137.156 Name: deb.rr.devuan.org Address: 195.85.215.180 Name: deb.rr.devuan.org Address: 200.236.31.1 Name: deb.rr.devuan.org Address: 95.216.15.86 Name: deb.rr.devuan.org Address: 5.9.122.185 Name: deb.rr.devuan.org Address: 158.69.153.121 Name: deb.rr.devuan.org Address: 131.188.12.211 Name: deb.rr.devuan.org Address: 130.225.254.116 Name: deb.rr.devuan.org Address: 141.84.43.19 Name: deb.rr.devuan.org Address: 2001:4ca0:4300::1:19 Name: deb.rr.devuan.org Address: 2001:e42:102:1704:160:16:137:156 Name: deb.rr.devuan.org Address: 2a01:4f8:162:7293::14 Name: deb.rr.devuan.org Address: 2607:5300:61:95f:7283:11d9:f86:e691 Name: deb.rr.devuan.org Address: 2a02:2a38:1:400:422a:422a:422a:422a Name: deb.rr.devuan.org Address: 2001:638:a000:1021:21::1 Name: deb.rr.devuan.org Address: 2a0a:e5c0:2:2:400:c8ff:fe68:bef3 Name: deb.rr.devuan.org Address: 2a01:9e40::180 Name: deb.rr.devuan.org Address: 2a01:4f9:2a:fa9::2 Name: deb.rr.devuan.org Address: 2801:82:80ff:8000::2 Name: deb.rr.devuan.org Address: 2a01:4f8:140:1102:2b76:955d:b48f:bdf3 Name: deb.rr.devuan.org Address: 2001:878:346::116 but I'm able to reach with IPV4. Maybe your resolver cache? I've added this lines to my unbound.conf forward-zone: # #forward-first: yes name: "deb.devuan.org" # forward-tls-upstream: yes forward-addr: 8.8.4.4 forward-addr: 8.8.8.8 and this seems to have fixed issues I had with resolved addresses being to old. Hope this helps. Ciao, Tito _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
