>
> > 5) There is no route for this IPv4 packet [which is actually an ICMPv6
> > error] as determined by the IPv4 routing table. An ICMPv4 error is
> > generated.
> >
> > 6) The ICMPv4 error is converted to an ICMPv6 error so that it can
> > be sent to the original IPv6 sender [router itself].
> >
> > Note that step (5) and step (6) are the similar to step (2) and (3)
> > and will continue forever till the ttl drops to zero.
> >
> > At step (5) we are generating an ICMPv4 error for the ICMPv6 error.
>
> no, you're generating an icmpv4 error for an tunnelled ipv6 packet
>
Agreed.
> > At step (6) we are generating an ICMPv6 error for the ICMPv6 error.
> >
> > Should step (5) or step (6) detect this and drop the packet ?
>
> step (5): no.
>
> step (6): yes. you should not send icmp errors in response to icmp
> errors.
I just wanted to point out that you can't convert ICMPv4 error to
ICMPv6 error blindly. You need to check to see the inner packet.
May be it is very obvious which i missed :-)
-mohan
>
> - Bill
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page: http://playground.sun.com/ipng
> FTP archive: ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to [EMAIL PROTECTED]
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
