>> >Handle IFF_ALLMULTI correctly.  We can now cope with multicast, but for
>> >some reason DAD fails when starting IPv6.
>> 	i guess the driver (or chip) is getting outgoing multicast packet
>> 	from itself, into inbound path
>That was what it looked like to me, yes.
>> (= not IFF_SIMPLEX behavior).
>But the driver doesn't set IFF_SIMPLEX:
>ea0: flags=8263<UP,BROADCAST,NOTRAILERS,RUNNING,ALLMULTI,MULTICAST> mtu 1500
>        address: 00:02:07:01:08:30
>        inet 172.17.11.33 netmask 0xffffff00 broadcast 172.17.11.255
>        inet6 fe80::202:7ff:fe01:830%ea0 prefixlen 64 duplicated scopeid 0x1

	not too sure about this, but sys/net/if_ethersubr.c may need to do
	something about IFF_SIMPLEX and multicast packet on input?

itojun