Re: Regression after changes for mounts from IPv6 addresses introducing delays

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


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
> > 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 . Yes this is nto
the IPv6 address which the server has in practice.


[Index of Archives]     [Linux Filesystem Development]     [Linux Ext4]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux