On Thu, Oct 10, 2002 at 09:14:45AM +0900, Yuji Sekiya wrote:
> At Thu, 10 Oct 2002 01:04:39 +0100,
> Derek Fawcus <dfawcus@xxxxxxxxx> wrote:
> > Turn on 'debug ipv6 nd', 'debug ipv6 icmp', 'debug ipv6 pack d'
> > Then do 'ping ipv6' specify a link local of say fe80:1910::10 and
> > an egress interface, and watch what happens.
> Oct 10 09:09:15: ICMPv6-ND: DELETE -> INCMP: FE80:1910::10
> Oct 10 09:09:15: ICMPv6-ND: Sending NS for FE80:1910::10 on FastEthernet4/1
> Oct 10 09:09:15: IPV6: source FE80::201:64FF:FEA3:ED55 (local)
> Oct 10 09:09:15: dest FF02::1:FF00:10 (FastEthernet4/1)
> Oct 10 09:09:15: traffic class 224, flow 0x0, len 72+8, prot 58, hops
> 255, originating
> Oct 10 09:09:15: IPv6: Sending on FastEthernet4/1
> Oct 10 09:09:15: IPv6: Encapsulation failed
> Encapsulation failed ... ??? :-)
Well there was no one to respond to the NS, so it couldn't figure out
what dest MAC address to shove in the ethernet packet. Hence the
ethernet encap failed.
Say if you sent such a packet over the link to the router, and it
tried to forward it without the neighbour being there, you should
get an ICMP error generated.
But anyway it was trying to resolve a neighbour entry, if someone
responded, it'd have sent the packet.
Now try it with a box on the link which will respond to the NS for that