Scott Dier <dieman+tclug at ringworld.org> wrote: > > * Mike Hicks <hick0088 at tc.umn.edu> [010805 14:50]: > > mike at hardrock:~$ ping6 www.kame.net > > PING www.kame.net(apple.kame.net) 56 data bytes > > >From 3ffe:b80:139:1::1: Destination unreachable: Address unreachable > > >From 3ffe:b80:139:1::1: Destination unreachable: Address unreachable > > > > --- www.kame.net ping6 statistics --- > > 2 packets transmitted, 0 packets received, 100% packet loss > > mike at hardrock:~$ traceroute6 www.kame.net > > traceroute6 to kame220.kame.net (2001:200:0:4819:280:adff:fe71:81fc) > from > > 3ffe:b80:139:1:2a0:24ff:fe35:b9f8, 30 hops max, 16 byte packets > > 1 3ffe:b80:139:1::1 (3ffe:b80:139:1::1) 0.807 ms !H 0.66 ms !H > 0.587 > > ms !H > > The eth0 interfaces on both my router and my client box have two inet6 > > addresses, one link-local (/10 with ff80 prefix) and the other global > > (/64). > > Some ideas: > > A) I dont have an address on my internal interface, with just a > link-local it works. Yeah, I don't think that matters, though, as the client system uses the router's link-local address as the default route. However, I did delete that address for a test, and things sort of seemed to kind of work better. mike at hardrock:~$ traceroute6 www.kame.net traceroute6 to kame220.kame.net (3ffe:501:4819:2000:280:adff:fe71:81fc) from 3ffe:b80:139:1:2a0:24ff:fe35:b9f8, 30 hops max, 16 byte packets 1 3ffe:b80:2:676::2 (3ffe:b80:2:676::2) 0.735 ms !H 0.672 ms !H 1.255 ms !H That's the address on my sit1 interface (my end of the IPv6-in-IPv4 tunnel) > B) Set 2000::/3 to your 'defaultroute' interface. Yeah, dont ask, its > something that the developers did. Could you clarify which interface on which system? > C) use an usagi kernel. Search for them on gooogle. I'll take a look at that, but I'd like to fiddle a bit with a stock kernel first, just to see if it's possible to get things to work `out of the box'.. > D) I had to add the 'subnet' to the route on my eth0 > So like, i put my prefix in and gave it dev of my internal network > interface... This was the one pitfall for me. You mean the /64 network? It looks like that's already routed to eth0: [mike at 3po][~]$ ip -f inet6 route 3ffe:b80:2:676::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 3ffe:b80:139:1::/64 dev eth0 proto kernel metric 256 mtu 1500 3ffe:b80:139::/48 dev eth0 metric 1 mtu 1500 fe80::/10 via :: dev sit1 proto kernel metric 256 mtu 1480 fe80::/10 dev eth0 proto kernel metric 256 mtu 1500 ff00::/8 dev sit1 proto kernel metric 256 mtu 1480 ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 default dev sit1 metric 1 mtu 1480 unreachable default dev lo metric -1 error -101 And just for completeness, my client box mike at hardrock:~$ /sbin/ip -f inet6 route 3ffe:b80:139:1::/64 dev eth0 proto kernel metric 256 expires 2591556sec mtu 1500 fe80::/10 dev eth0 proto kernel metric 256 mtu 1500 ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 default via fe80::260:8ff:fe42:97a6 dev eth0 proto kernel metric 1024 expires 1356sec mtu 1500 unreachable default dev lo metric -1 error -101 -- _ _ _ _ _ ___ _ _ _ ___ _ _ __ 668 - Neighbor of the / \/ \(_)| ' // ._\ / - \(_)/ ./| ' /(__ Beast \_||_/|_||_|_\\___/ \_-_/|_|\__\|_|_\ __) [ Mike Hicks | http://umn.edu/~hick0088/ | mailto:hick0088 at tc.umn.edu ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20010806/3c8c2343/attachment.pgp