Re: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address

To: tech-net%netbsd.org@localhost
Subject: Re: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
From: mlelstv%serpens.de@localhost (Michael van Elst)
Date: Sun, 8 Aug 2021 04:55:30 -0000 (UTC)

kardel%kardel.name@localhost (Frank Kardel) writes:

>Is there anyone willing to look at the fix before I commit?
>The MTU bug prohibits data transfer as the write(v) systemcall
>fails with EMSGSIZE(40).
>https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=56348

Mapped IPv4 addresses are considered harmful on the wire, that's
why /etc/rc.d/network sets a route that rejects such packets.

But this is just a (changeable) policy. How does the fix work on a
machine without IPv4 where mapped addresses might be wanted (RFC1933) ?

Follow-Ups:
- Re: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
  - From: Frank Kardel

References:
- PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
  - From: Frank Kardel

Prev by Date: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
Next by Date: Re: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
Previous by Thread: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
Next by Thread: Re: PR: MTU discovery fails with IPv6 sockets bound to IPv4 mapped address
Indexes:

Home | Main Index | Thread Index | Old Index