On Sat, Nov 07, 2020 at 03:58:51PM +1100, [email protected] wrote: > [root@owl /etc/apt]# apt-get install inxi > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following additional packages will be installed: > hddtemp libglew2.1 lm-sensors mesa-utils tree > Suggested packages: > libcpanel-json-xs-perl | libjson-xs-perl libxml-dumper-perl glew-utils > fancontrol read-edid i2c-tools > The following NEW packages will be installed: > hddtemp inxi libglew2.1 lm-sensors mesa-utils tree > 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. > Need to get 731 kB of archives. > After this operation, 2,625 kB of additional disk space will be used. > Do you want to continue? [Y/n] y > Err:1 http://ftp.au.debian.org/debian bullseye/main amd64 hddtemp amd64 > 0.3-beta15-53 > Connection failed [IP: 2001:388:1034:2900::25 80] ^^^^^^^^^^^^^^^^^^^^^^
OK, that's clearly using the IPv6 address for ftp.au.debian.org Does your ISP support IPv6? If not, then force apt to use ipv4 as i mentioned in my last message. BTW, if you don't know how to recognise an ipv4 or ipv6 address, it's pretty easy. ipv4 address are short, usually printed in decimal, with **exactly** four groups of 8-bit decimal numbers (i.e. 0 to 255), separated by periods ".". e.g. 192.168.1.1. sometimes with an optional netmask suffix like /24 or /32. ipv6 addresses are longer, usually printed in multiple groups of four hexadecimal digits (i.e. 16 bits worth), separated by colons. e.g. 2001:388:1034:2900::25 see: https://en.wikipedia.org/wiki/IPv4#Addressing https://en.wikipedia.org/wiki/IPv6_address While it's useful to know the basics of IP networking, you don't actually need to understand all the details. For practical purposes, you really only need to know if your ISP support ipv6 routing or not. If not, then disable it (at least on your uplink interface). Most ISPs still do not support ipv6. This is because they're slack-arse lazy bastards who find the shortage of ipv4 addrress space convenient for limiting what their customers do on the internet. > Using host au debian is not found: > > [ben@owl ~]$ host ftp.au.debian.org/ > Host ftp.au.debian.org/ not found: 3(NXDOMAIN) that's not a domain name. that's just a string ending in / host doesn't know what to do with a string ending in a / > [ben@owl ~]$ host http://ftp.au.debian.org > Host http://ftp.au.debian.org not found: 3(NXDOMAIN) that's not a domain name either. That's a URL. host doesn't know what to do with a URL either. > The nz debian is found. > [ben@owl ~]$ host ftp.nz.debian.org that's a domain name. host knows what to do with one of those. which is why it worked: > ftp.nz.debian.org is an alias for mirror.fsmg.org.nz. > mirror.fsmg.org.nz has address 163.7.134.112 > mirror.fsmg.org.nz has IPv6 address 2404:138:4000:: > When I changed sources.list to ftp.nz.debian.org, and tried installing inxi, > the error was: > > [root@owl /etc/apt]# apt-get install inxi > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package inxi that's because you didn't update the packages lists after changing the repo. when you change sources.list, you have to run "apt-get update" (or "apt update", etc) > Testing with the Force config. I used the cowsay program as the test: > [...it worked...] not surprising. the problem was, as I suspected, that your machine was using the mirror's IPv6 IP address rather than IPv4. > I purged cowsay and then tried the nz mirror but it failed: > > [root@owl /home/ben/Downloads]# apt-get -o Acquire::ForceIPv4=true install > cowsay > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package cowsay again, this is because you didn't run "apt-get update" after changing sources.list > Whilst going through the process that was suggested and running > the commands above, I returned to Firefox, and it now brings up > http://ftp.au.debian.org/. The only extra thing that I have done which is > not described above is to return the /etc/hosts file that I use to its > original from the Pollock hosts file. > > -------start /etc/hosts------- > 127.0.0.1 localhost > 127.0.1.1 owl > > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > -------end /etc/hosts--------- that hosts file looks OK. And isn't relevant here because it doesn't have entries for either ftp.au.debian.org or ftp.nz.debian.org. Dunno why you're calling it a "Pollock" hosts file. > I have now written the /etc/apt//apt.conf.d/zzz-ipv4.conf with the ipv4 > Force config as suggested. > > The nz mirror still fails. I would really like to be able to change mirrors > if I need to in the future. Just remember to run 'apt-get update' whenever you change sources.list. In fact, you should be running it before you do any apt/aptitude/apt-get/etc operations like "upgrade", "dist-upgrade", "install", etc. Not before every single apt-get command, but at least once for any day you intend to install or upgrade packages, so that apt is working with an up to date Packages list and knows WHAT packages & versions are available and WHERE they can be downloaded from. > Is there anything in the results that looks like it can help? > > I'm wondering if this is an intermittent error of DNS, and if so, what I > could do about it. If you don't use IPv6 at all, you could disable it in the kernel. e.g. by adding IPV6_DISABLE=1 to the GRUB_CMDLINE_LINUX entry in /etc/default/grub and then running "update-grub"...the next time you reboot, ipv6 will be disabled. It's important to **ADD** it, not replace whatever might already be in GRUB_CMDLINE_LINUX. e.g. on one of my systems, I have this: GRUB_CMDLINE_LINUX="boot=zfs amd_iommu=on iommu=on amd_iommu_dump=hw IPV6_DISABLE=1 log_buf_len=1M" I do this because my ISP doesn't support ipv6 and lots of software will happily try to use an ipv6 address if a dns lookup returns an AAAA record and the network interface has an ipv6 address, so it's just easier to disable ipv6 entirely in the kernel. Note that at some point in the far distant future when the promised day arrives and ipv6 is used everywhere (or maybe earlier if your ISP starts supporting it), you'll have to undo this. This has been "imminent" for years now and is likely to remain imminent for the forseeable future. IMO, this is not likely to happen until spyware corporations like LG and Samsung and thousands of other IoT companies lobby/demand/bribe ISPs to get off their arses and implement ipv6 so that it's easier for them to access their smart tvs, fridges, toasters etc without annoying things like NAT getting in the way. craig -- craig sanders <[email protected]> _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
