Hi, First I have to describe the network, we have our core router (core for AS6830) that is connected to a switch, on that switch we have some computers connected, one solaris 8 (future), raiden (linux 2.2.19) and initio (linux 2.4.11). The router run ND to give out IPv6 IP's to all the computers there. All 3 of the machines get a IP correct and everything worked fine. Some days/weeks ago I started to notice odd lag on my IRC client from raiden (ipv6 of course), got time a few days ago to look into it and did some random traceroute and saw this: traceroute6 to irc.ipv6.chello.no (2001:730:3:1:a00:20ff:fe0c:4f01), 30 hops max, 60 byte packets 1 2001:730:0:2:290:86ff:fef6:a408 (2001:730:0:2:290:86ff:fef6:a408) 0.679 ms 0.601 ms 0.461 ms 2 initio.ipv6.chello.com (2001:730:0:2:2d0:b7ff:fe3e:aae2) 0.549 ms 0.507 ms 0.416 ms 3 3ffe:80b0:1002:1002:2b0:8eff:fe31:8038 (3ffe:80b0:1002:1002:2b0:8eff:fe31:8038) 0.824 ms 0.852 ms 0.783 ms <world> Question is, how did initio.ipv6.chello.com end up there? It should gone stright to hop 3 which is the router. The router advertise 3 prefixes with the eui-64 standard. Config of raiden is linux 2.2.19 and running nothing related to IPv6 except that it pick up an IP address. Initio do the same as raiden, but on top of that I'm doing a native peering (BGP) with the router. I'm using zebra with a zero config, that is it's supressing (not using) ND. And to be able to route traffic out through the ip6-in-ipv4 tunnels from initio I need to have forwarding enabled. But that's about it. But somehow have raiden found out that it should use initio insted of the router as it's next_hop... any idea why? Looks like something in ND is broken. Or will the answer be, upgrade to the latest 2.4-kernel? Thanks anyway, ------------------------------ Roger Jorgensen | IRC: James_B rogerj@stud.cs.uit.no | - IPv6 is The Key! http://www.cs.uit.no/~rogerj | roger@jorgensen.no ------------------------------------------------------- - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
