On Wed, Jan 20, 2021 at 11:59:46PM -0600, David Wright wrote: > As far as the address is concerned, fe80::1 is perfectly formed, > but ambiguous. Is that what your jessie error message used to say?
The error was one of the usual kernel errors (-EINVALID probably), see below. Actually, stretch does the same (Linux ns2 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 GNU/Linux): root@ns2 ~ # ping6 fe80::1 connect: Invalid argument root@ns2 ~ # ping6 fe80::1%2 PING fe80::1%2(fe80::1%eth0) 56 data bytes 64 bytes from fe80::1%eth0: icmp_seq=1 ttl=255 time=0.423 ms 64 bytes from fe80::1%eth0: icmp_seq=2 ttl=255 time=0.332 ms 64 bytes from fe80::1%eth0: icmp_seq=3 ttl=255 time=0.305 ms 64 bytes from fe80::1%eth0: icmp_seq=4 ttl=255 time=0.355 ms fe80::1 is specifically a link-local scope, a bit like if you try to access a class variable without telling in what class it is.
