[EMAIL PROTECTED] writes: > KAME code has a special code (disabled by default) for this case, like > - suppose I am a router. if the packet comes in from interface Ix, > and goes out again to Ix, and interface Ix is a p2p link, I do not > forward the packet. instead, I'd emit ICMPv6 no route to > host. Won't this result in ICMP no route messages also being generated for packets being forwarded back out the same link via the routing header? I.e., perfecly legal packets that don't cause problems get dropped? Seems like if such a rule were to be defined, it needs to be more nuanced than written above. Thomas -------------------------------------------------------------------- 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] --------------------------------------------------------------------
- Re: nonexisting destination on p2p link Ole Troan
- Re: nonexisting destination on p2p link itojun
- RE: nonexisting destination on p2p link Richard Draves
- Re: nonexisting destination on p2p link Robert Elz
- Re: nonexisting destination on p2p link itojun
- Re: nonexisting destination on p2p link Robert Elz
- Re: nonexisting destination on p2p link itojun
- Re: nonexisting destination on p2p link Robert Elz
- Re: nonexisting destination on p2p link Thomas Narten
- Re: nonexisting destination on p2p lin... JINMEI Tatuya / 神明達哉
- Re: nonexisting destination on p2p link Pekka Savola
- Re: nonexisting destination on p2p link JINMEI Tatuya / 神明達哉
- Re: nonexisting destination on p2p link Tim Hartrick
- Re: nonexisting destination on p2p link itojun
- Re: nonexisting destination on p2p link Tim Hartrick
- Re: nonexisting destination on p2p link itojun
- Re: nonexisting destination on p2p lin... Erik Nordmark
- Re: nonexisting destination on p2p link Erik Nordmark
