Subject: Re: Neighbour Discovery Bug?
To: Feico Dillema <dillema@acm.org>
From: None <itojun@iijlab.net>
List: current-users
Date: 07/22/1999 03:22:53
>Forgot to mention: the setup still has a problem. without ND (as IPv4
>equivalent of proxy-arp) other hosts on the network with prefix
>3ffe:2a00:100:3002::/64 (e.g. ethernet xl0 or other tunnels) cannot
>get to the `link-local' hosts behind a tunnel. (again for me not a
>real problem, as I can give each tunnel a different prefix, but
>thought I'd mention it `for the archives').
Now I see what you meant. You are using same prefix for both
tunnel and the ethernet (I should have asked you to draw a diagram).
Sorry this does not work at this moment. This complicates many
things, for example scope of link-local addresses. Steve Deering
likes this kind of "subnet over multiple link, connected by router"
configuration, but I believe specification is not ready for this.
(if "link-local" scope is just one link, like tunnel, what happens to
DAD, RA, or ripng packets between ethernet 3ffe:2a00:100:3002::/64 and
tunnel 3ffe:2a00:100:3002::/64?)
itojun
==+=== 3ffe:2a00:100:3001::/64
| vx0
pastaws0 ---------------------------------+ tunnel
| xl0 |
==+=== 3ffe:2a00:100:3002::/64 |3ffe:2a00:100:3002::/64
spam