neighbor discovery problem

[Pete French]

> Since I added IPv6 to my network, and started really using it, I'm seeing
> some strange things happening.
>
> For instance, I'm on machine 2a01:678:1:443::443, and I do :
>
> $ traceroute6 -n 2a01:678:100:2::
> traceroute6 to 2a01:678:100:2:: (2a01:678:100:2::) from
> 2a01:678:1:443::443, 64 hops max, 12 byte packets
>  1  2a01:678:1:443::  0.636 ms  0.602 ms  0.525 ms
>  2  2a01:678:1:443::  2999.665 ms !A  2999.636 ms !A  2999.680 ms !A
>
> 2a01:678:1:443:: is it's default gateway, and is also directly connected to
> 2a01:678:100:2::, but it does not seem to be able to contact it.

What are your prefix lengths on the various interfaces, and does
2a01:678:100:2:: have a route back to 2a01:678:1:443::443 ? If you
can show us the config on the interfaces of the three machines then
we might be able to get a better idea. I am imagining how you have these
three boxes connected in my head, but nothing beats an explanation plus
the config :-)

> Maybe I'm doing something wrong, but, well, I can't seem to find ou what.
>
> 2a01:678:1:443::443 is a 7.0
> 2a01:678:1:443::    is a 6.2
> 2a01:678:100:2::    is a 6.0

I've used all of those with IPv6 and they work fine, it's most likely
a small config problem. I had a lot of frustrations with IPv6 when I
started using it - though now it is working I wouldn't be without it.

-pete.