Hi, Karsten.
Please check RFC 4862 (IPv6 Stateless Address Autoconfiguration).
Section 5.4.5 says,
909 If the address is a link-local address formed from an interface
910 identifier based on the hardware address, which is supposed to be
911 uniquely assigned (e.g., EUI-64 for an Ethernet interface), IP
912 operation on the interface SHOULD be disabled. By disabling IP
913 operation, the node will then:
914
915 - not send any IP packets from the interface,
916
917 - silently drop any IP packets received on the interface, and
918
919 - not forward any IP packets to the interface (when acting as a
920 router or processing a packet with a Routing header).
Thanks,
On Tue, 8 Jan 2008 19:11:12 +0100
Karsten Keil <kkeil@suse.de> wrote:
> Hi,
>
> I tried the latest Selftest Beta and now I got failed tests (target passed
> Selftest 1.4.9 without any error).
>
> Failing test are in IPv6 Stateless Address Autoconfiguration:
>
> 3 Part B: NUT receives DAD NS (target == NUT)
> 5 Part D: NUT receives DAD NA (target == NUT)
> 14 Part I: NUT receives valid DAD NS (Reserved Field)
> 15 Part J: NUT receives valid DAD NS (contains TLL)
> 23 Part H: NUT receives valid DAD NA (Reserved Field)
> 24 Part I: NUT receives valid DAD NA (contains SLL)
>
>
> It seems that it all fails in the new added
> seqVrfyIpOperation($IF, $IF1);
>
> call because it get a DAD NS for its Global address.
>
> I do not understand why it should not get this packet.
>
> --
> Karsten Keil
> SuSE Labs
>
>
------------------------------------------------------------------------
Yukiyo Akisada <akisada@tahi.org>