Hi. On Thu, Feb 22, 2018 at 10:11:24AM +0100, Roger Price wrote: > On Tue, 20 Feb 2018, Reco wrote: > > On Tue, Feb 20, 2018 at 12:23:06PM +0100, Roger Price wrote: > > > Later the installation hangs with the message: > > > > > > in-target: Failed to fetch > > > > > > http://debian.mirrors.ovh.net/debian/dists/stretch/main/i18n/Translation-en > > > Cannot initiate the connection to debian.mirrors.ovh.net:80 > > > (2001:41d0:202:100:213:32:5:7). - connect (101: Network is unreachable) > > > [IP 2001:41d0:202:100:213:32:5:7 80] > > > > > > There is no mention of IPv4 and I do not have IPv6. > > > > Of course you have IPv6, probably in the form of SLAAC/RA. How else > > Linux kernel used in the installer would know which IPv6 address to use > > and which IPv6 route to choose to 2001:41d0:202:100:213:32:5:7. > > I have a TP-Link TL-WR1043ND v3 router sold as IPv6 capable. I selected > SLAAC and the following was reported in the system log: > > Feb 19 23:41:47 IPv6 NOTICE getSlaacParameters 477 sscanf address and > prefix error > Feb 19 23:43:32 IPv6 INFO IPv6 is not enabled.
Curious, but wonders cannot happen by themself. > IPv6 management in the router has hung and I cannot select an alternative to > SLAAC. Thank you, added that particular model to my 'Do Not Buy Ever' list. > On the EeePC Ctl-Alt-F3 /dev/tty3: > ~ # ip address > 3: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> ... > ... > inet 10.218.0.100 scope global enp0s4 > inet6 fe80::22cf:30ff:fe10:43fd/64 scope link > > The "fe" at the beginning of the IPv6 address says that this is not capable > of working with the public IPv6 network. There's one crucial detail that's missing here. I agree that fe80 designates link-local IPv6 (they don't put "scope link" there for nothing), but what about routing? I.e. I'm curious about the output of "ip -6 ro l". Reco
