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

Hi,

On Sun, Jul 20, 2003 at 10:45:26PM +0700, Robert Elz wrote:

> I haven't yet attempted to look and see why that NA was ignored, instead
> of causing DAD to "fail" (or "succeed" if you like, since it did manage
> to detect a duplicate address), which should have caused (I believe) ifco=
nfig
> to report an error (it didn't).
>=20
> Is this something that is known not to work?

Uhm... I've seen occurences of "IPv6 doesn't work" that pointed me at=20
a bug in multicast address handling on a specific hardware driver.

In my case it was something like "last multicast address configured doesn't
work" or "first multicast address configured doesn't work" - sort of a=20
off-by-one-error. Just to make sure, please check that the suspected culprit
does pong to multicast pings to ff02::1 with its normal configuration, or
after adding the dead:beef address.

(The interesting difference about multicast vs. IPv6 is, that non-broadcast
multicasts are part of the infrastructure, while in IPv4, to the end user
they're only part of experimental protocols that are somehow expected to
mysteriously fail, such formerly, driver bugs in handling of the multicast
address list sometimes weren't detected for a long time.)

Regards,
	Ignatios

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

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPxr3bzCn4om+4LhpAQH8Dgf+N7icpF4kyUhH5rEz8dLbtcZuymiAzeNh
mdz3OyQ5cbBYTyqoLubi+tGgPwBz8NXOs5xdaYtMMwKhl0ijRPTlzWwzUDi7OrvC
ncBLPEpYSSSUo0g9xR6kNwO5pYG+MGqGFX46XLqYGlDWEeHPYGbLUc306594wCyP
fwpijBv7JO2ot8Qfy6oDAEN9lByuJFBFqkiOx/+9MFZYtyxTYxrMoFQIYU47z0+M
kI2XKkx+hHF2642lmKDgfy02dzr542q8/YHSMVnBW5MUITq6h3IsDpa4ZDn3NsgT
7e/lKwIQXE0RKVVAcHVjEgNXgO+ioA6ja91FouejDf/FTN8ptV7i/A==
=2jQ1
-----END PGP SIGNATURE-----

--KFztAG8eRSV9hGtP--