With ospf6d, routes are added using link-local addresses. ICMP6 messages are generated with a source of, I think, the local address associated with the route to the recipient, so with a couple of hops in the internal network it results in traceroutes looking like
$ traceroute6 -n www.google.com traceroute6 to www.google.com (2a00:1450:4009:80f::2004), 64 hops max, 60 byte packets 1 fe80::5606:33d8:d784:cd2f%vlan701 (fe80::5606:33d8:d784:cd2f%vlan701) 0.519 ms 1.547 ms 0.417 ms 2 * * * 3 * * * 4 2001:728:0:5000::55 7.843 ms 8.236 ms 7.391 ms [...] The first hop works (ugliness aside) because the link-local is directly connected, the next ones don't because the ICMP response are sourced from a link-local addresses (to match the route to the destination) but these aren't allowed to be forwarded by routers. (And once packets have left the AS, things work as expected on global addresses). What's anyone else doing? Just living with it or has anyone figured a way to make it nicer? I'd like to reply with either a global scope address for the interface, or a loopback address, I didn't get anywhere with PF translation though.
