On 10/7/23 14:09, Salvatore Bonaccorso wrote:
Hi Ian,
On Mon, Jul 10, 2023 at 10:53:31AM +0800, Ian Kent wrote:
On 9/7/23 22:57, Salvatore Bonaccorso wrote:
Hi
The following sort of regression was noticed while updating a client
running Debian buster (with autofs 5.1.2 based) to Debian bullseye
(5.1.7 based autofs), but verified it's still present with 5.1.8. The
folloing setup is present:
There is a NFS server, dualstacked, with both public IPv4 and IPv6
addresses resolvable in DNS. As I cannot put the public IPs here in
the report, let's assume It is called nfs-server with addresses
192.168.122.188 and fc00:192:168:122::188.
I assume the IPv6 address here is not what's used in practice. It
doesn't look valid, it doesn't look like an IPv4 mapped address, what
is it, how was it constructed?
I'm sorry this was just me trying to use something valid from
https://en.wikipedia.org/wiki/Unique_local_address . Yes this is nto
the IPv6 address which the server has in practice.
Yes, it's been hard over time given the available IPv6 support has been
poor and setting up locally has always been a problem for me.
But, as I say, my ISP is there now so I should be good to go.
Ian
