[j-nsp] ipInIp interface got the same IPV6 address on both end?

[Alexander Arsenyev (GU/ETL)]

<quote>
OSPFv3 use RID to run and build LSDB. The interface addressing is just information carried by protocol. This is oposite to OSFPv2 and very similiar to ISIS (IPv4). So this can be a reason of working OSPFv3 and not working RIPng.
</quote>

RFC2080 states that RIPng's datagram's IPv6 source address should be checked to see whether the datagram is from a valid neighbor; the source of the datagram must be a link-local address and not one of the router's own addresses. You have identical link-local IPv6 addresses on both ends of IPIP tunnel and I suspect that after stripping off the tunnel encapsulation the RIPng examines the source IPv6 address and finds it to be its own link-local IPv6 address therefore drops the RIPng update. 
AFAIK, OSPFv3 uses IPv4-style 32-bit router-ids to identify neighbours as opposed to common subnet IP addresses (RFC2740 section 2.11).

<quote>
In your case let's try to manualy assigne address to link and do not use eui-64 automagic.
</quote>
I'd second that.

HTH
Cheers
Alex