On Mon, 26 Jan 2004, Andreas Jellinghaus wrote: > Hi Ville, Hello Anreas, let's hope we can soon figure out what the problem is ;) > on both machines: > ip6_tnl_set_cap entered: 1d 1d 0d > ip6_tnl_set_cap inside: 1d 1d 0d > ip6_tnl_set_cap final: 1d 1d 0d > ip6_tnl_set_cap put Ok, it looks like both addresses (laddr and raddr) are global unicast addresses based on ltype and rtype, which seems correct. Since they are both unicast addresses, but p->flags isn't updated it must mean that ip6_chk_addr() fails on at least one of the addresses. The first check is to make sure the node is allowed to send and receive packets using laddr. This is done by checking that the local node has the address configured. The second check is to avoid local routing loops. This is done by requiring that raddr is not configured to any interface on the local node. > shall I printk laddr, raddr and the results > of ipv6_chk_addr as well? Yes, at least print the results of both ip6_chk_addr() calls, since this should tell us which call fails. > the test was: > > + ip -6 addr add 4000::1 dev wlan0 This should probably be 4000::1/64 :) Not sure that it actually matters, though. Regards, Ville -- Ville Nuorvala Research Assistant, Institute of Digital Communications, Helsinki University of Technology email: vnuorval@tcs.hut.fi, phone: +358 (0)9 451 5257 - : 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
