--Q68bSM7Ycu6FN28Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 02, 2004 at 08:34:50PM +0100, Konstantin KABASSANOV wrote:
> Well, I've probably taken the wrong way to debug but:
>=20
> >ping6 -s 1300 my-ipv6-address
>=20
> gives me icmp packets fragmented to payload 1232 and additional fragments
> of 76 bytes...

I can reproduce this with a 1.6.2/arm32 pinging 1.6.2/i386.

However, when I produce UDP packets (using traceroute6 ) fragmentation
starts at "datasize" 1428 bytes, I think as expected.

Now, for the ICMPv6 handling:=20

what _I_ am seeing is that the _reply_ is fragmented, but not the request.
(Konstantin: is this what you are seeing, too?)

So I think the ICMPv6 reply machinery limits to the minimum IPv6 MTU of=20
1280 bytes, always, which might conform to RFC2463 on a quick reading.
What looks odd is that it fragments, instead of discarding the data
going over the limit (which I'd expect for ICMPv6 special handling).

Does anybody know?

Regards,
	-is

--Q68bSM7Ycu6FN28Q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFBr3RrN4tiz3B8hB0RAtu9AKDBzxIhMs81Zap7EZOGPJPx6upaEwCgrcIY
Yw126Asgrd7bc6UU30ECS1U=
=swLJ
-----END PGP SIGNATURE-----

--Q68bSM7Ycu6FN28Q--