How long is reasonable to fix a routing issue in IPv6?

The below has been on going for over a week (yes it has been reported to HE) and the IETF). Not returning time exceeded really make debugging routing problems hard. Mark traceroute6 -lI www.ietf.org traceroute6 to www.ietf.org (2001:1890:1112:1::1e) from 2001:470:1f00:::5a1, 64 hops max, 1

Re: How long is reasonable to fix a routing issue in IPv6?

If those interim hops are IPv4 only nodes part of 6/PE there could be a few things going on here. 1) Juniper u-RPF for family inet6 drops the mapped-v4-v6 source packets generated by a P/PE router 2) FreeBSD (8.2 at least) doesn't seem to like mapped-v4-v6 source packets with its default tracer

Re: How long is reasonable to fix a routing issue in IPv6?

In message <9634aa8c-c8fd-4afe-a888-82c9c3266...@puck.nether.net>, Jared Mauch w rites: > If those interim hops are IPv4 only nodes part of 6/PE there could be a = > few things going on here. > > 1) Juniper u-RPF for family inet6 drops the mapped-v4-v6 source packets = > generated by a P/PE route